owner stringclasses 14
values | repo stringclasses 14
values | id int64 116k 4.61B | issue_number int32 1 181k | author stringlengths 1 39 | body stringlengths 1 262k | created_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:16:18 | updated_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:22:56 | reactions unknown | author_association stringclasses 5
values |
|---|---|---|---|---|---|---|---|---|---|
vuejs | core | 781,506,167 | 3,256 | posva | I read it. It doesn't do what you say | 2021-02-18T17:23:42 | 2021-02-18T17:23:42 | {} | MEMBER |
vuejs | core | 781,856,526 | 3,225 | dependabot-preview[bot] | Superseded by #3260. | 2021-02-19T06:20:47 | 2021-02-19T06:20:47 | {} | CONTRIBUTOR |
vuejs | core | 781,858,067 | 3,263 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.57 KB (0%) |
| runtime-dom.global.prod.js | 26.96 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-19T06:23:51 | 2021-02-19T06:23:51 | {} | NONE |
vuejs | core | 781,926,576 | 3,264 | ustbhuangyi | > Another workaround, you can remove the changes to the state, see https://codepen.io/hcysunyang/pen/wvoeOaa
Haha, that's the reason why it looks strange. But I do need to do this | 2021-02-19T08:43:50 | 2021-02-19T08:43:50 | {} | CONTRIBUTOR |
vuejs | core | 782,919,712 | 3,273 | LinusBorg | Well, you define the injection as boolean, but it's a readonly ref containing a boolean. so typescript rightfully complains.
```ts
const logInKey = Symbol("is the user logged in") as InjectionKey<Readonly<Ref<boolean>>>
//or
const logInKey = Symbol("is the user logged in") as InjectionKey<typeof isLoggedIn>
``` | 2021-02-21T20:20:18 | 2021-02-21T20:21:22 | {
"+1": 1
} | MEMBER |
vuejs | core | 783,118,774 | 3,279 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.57 KB (0%) |
| runtime-dom.global.prod.js | 26.96 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-22T06:19:39 | 2021-02-22T06:19:39 | {} | NONE |
vuejs | core | 783,926,515 | 3,280 | HcySunYang | Duplicate of #2970? | 2021-02-23T05:46:51 | 2021-02-23T05:46:51 | {} | MEMBER |
vuejs | core | 778,992,560 | 3,080 | HcySunYang | I changed the implementation | 2021-02-15T06:51:01 | 2021-02-15T06:51:01 | {} | MEMBER |
vuejs | core | 781,299,072 | 3,252 | posva | You need to
```js
return () =>
h(toRender, {
attrs: { ...ctx.attrs },
})
```
so Vue can track you are reading `items` from `attrs` | 2021-02-18T12:09:26 | 2021-02-18T12:09:26 | {} | MEMBER |
vuejs | core | 781,780,562 | 3,255 | gryphonmyers | Oh, umm I just filed this same bug under vue-router: https://github.com/vuejs/vue-router-next/issues/778
You sure this is a core bug and not a bug with the implementation of router-view? | 2021-02-19T03:01:37 | 2021-02-19T03:01:37 | {} | NONE |
vuejs | core | 781,858,049 | 3,262 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.57 KB (0%) |
| runtime-dom.global.prod.js | 26.96 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-19T06:23:50 | 2021-02-19T06:23:50 | {} | NONE |
vuejs | core | 782,591,109 | 3,270 | HcySunYang | Workaround: As long as the component name in the template is not the same as the binding, there will be ok. | 2021-02-20T09:01:32 | 2021-02-20T09:01:32 | {} | MEMBER |
vuejs | core | 782,836,242 | 3,272 | malikzh | `reactive` does not work with arrays. And this feature request doesn't matter. | 2021-02-21T10:43:15 | 2021-02-21T10:43:15 | {} | NONE |
vuejs | core | 783,936,104 | 3,261 | dependabot-preview[bot] | Superseded by #3284. | 2021-02-23T06:09:46 | 2021-02-23T06:09:46 | {} | CONTRIBUTOR |
vuejs | core | 783,937,124 | 3,285 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.57 KB (0%) |
| runtime-dom.global.prod.js | 26.96 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-23T06:12:11 | 2021-02-23T06:12:11 | {} | NONE |
vuejs | core | 779,321,457 | 3,237 | AdrianoFSilva01 | Ok thank you for your time! | 2021-02-15T16:13:05 | 2021-02-15T16:13:05 | {} | NONE |
vuejs | core | 779,250,644 | 3,235 | LinusBorg | Ah, gotcha | 2021-02-15T14:16:31 | 2021-02-15T14:16:31 | {} | MEMBER |
vuejs | core | 779,315,053 | 3,237 | AdrianoFSilva01 | Thank you for the answer. What the best way to solve this then? | 2021-02-15T16:01:50 | 2021-02-15T16:01:50 | {} | NONE |
vuejs | core | 779,532,148 | 3,238 | HcySunYang | I'm not sure if this is intentional, but it seems reasonable that imports in normal scripts are not exposed to templates | 2021-02-16T01:55:01 | 2021-02-16T01:55:01 | {} | MEMBER |
vuejs | core | 783,057,667 | 3,274 | ZouHuaYi | With JSX support in templates, the syntax is much more flexible. For example, it can handle pre-rendered data that can be processed at the time of acquisition or computed, but this is not flexible after development. This is where React is great | 2021-02-22T03:53:12 | 2021-02-22T03:53:12 | {} | NONE |
vuejs | core | 783,117,900 | 3,275 | Ryan2128 | > Same workaround as [#3270 (comment)](https://github.com/vuejs/vue-next/issues/3270#issuecomment-782591109)
Yes, just change one of their name.
Thanks. | 2021-02-22T06:17:57 | 2021-02-22T06:17:57 | {} | NONE |
vuejs | core | 783,936,486 | 3,282 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.57 KB (0%) |
| runtime-dom.global.prod.js | 26.96 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-23T06:10:40 | 2021-02-23T06:10:40 | {} | NONE |
vuejs | core | 783,936,777 | 3,283 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.57 KB (0%) |
| runtime-dom.global.prod.js | 26.96 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-23T06:11:23 | 2021-02-23T06:11:23 | {} | NONE |
vuejs | core | 779,319,816 | 3,237 | LinusBorg | I don't know what you want to achieve so I don't have an answer to that.
If you need help, please use chat.vuejs.org andf ask the community. | 2021-02-15T16:10:21 | 2021-02-15T16:10:21 | {} | MEMBER |
vuejs | core | 781,502,301 | 3,256 | emirotin | Please read my description
It does what you say but it _also_ triggers an event when Ctrl is pressed
and released on its own which clearly contradicts the quote from the docs
which I provided
On Thu, Feb 18, 2021, 18:54 Eduardo San Martin Morote <
notifications@github.com> wrote:
> This is working as expected: it inc... | 2021-02-18T17:17:51 | 2021-02-18T17:17:51 | {} | NONE |
vuejs | core | 781,983,248 | 2,602 | rafaelsouzaf | @ferencbeutel4711 Could you find a solution? | 2021-02-19T10:23:45 | 2021-02-19T10:23:45 | {} | NONE |
vuejs | core | 783,835,022 | 2,851 | lijingfaatcumt | > > second we can pass arount the readonly by function toRaw and reactive and then operate the origin object, so the problem you said i pass around the readonly is has existing
>
> That's _explicitly_ doing hacky stuff. If you really need / want to, it's fine.
>
> The problem is that `reactive` is _implicitly_ ca... | 2021-02-23T02:30:54 | 2021-02-23T02:30:54 | {} | NONE |
vuejs | core | 783,925,888 | 3,280 | arpowers | @HcySunYang sure, close this one or the other to prevent duplication. I just wanted to surface the issue. | 2021-02-23T05:45:15 | 2021-02-23T05:45:15 | {} | NONE |
vuejs | core | 779,064,368 | 3,231 | HcySunYang | How to reproduce the problem? I opened the link you provided and no errors appeared | 2021-02-15T08:51:16 | 2021-02-15T08:51:16 | {} | MEMBER |
vuejs | core | 779,267,579 | 3,236 | asturur | oh good to know, this will serve as a reference for future fabricJS questions around VUE.
Thanks. | 2021-02-15T14:46:14 | 2021-02-15T14:46:34 | {} | NONE |
vuejs | core | 779,610,381 | 3,239 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.57 KB (0%) |
| runtime-dom.global.prod.js | 26.96 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-16T06:15:53 | 2021-02-16T06:15:53 | {} | NONE |
vuejs | core | 779,804,816 | 3,069 | floorish | The issue on Vite's repository has been closed: "This is a Vue core (compiler-sfc) bug and will be tracked/fixed in the vue-next repo."
https://github.com/vitejs/vite/issues/1626
Can this issue be reopened? | 2021-02-16T12:26:39 | 2021-02-16T12:27:19 | {} | NONE |
vuejs | core | 781,438,769 | 3,253 | p3k | thanks for the reply, @LinusBorg.
> code reuse should be achieved by extracting logic into functions that can be composed inside a component's setup function
would you have an example showing what you mean by this? like: here is an extend pattern, and here is the composition api implementing this pattern…?
at ... | 2021-02-18T15:48:27 | 2021-02-18T15:48:27 | {} | NONE |
vuejs | core | 781,856,809 | 3,155 | dependabot-preview[bot] | Superseded by #3261. | 2021-02-19T06:21:21 | 2021-02-19T06:21:21 | {} | CONTRIBUTOR |
vuejs | core | 781,880,852 | 3,255 | gryphonmyers | Seems like it - I'll close my dupe. Sorry for the noise! | 2021-02-19T07:10:54 | 2021-02-19T07:10:54 | {} | NONE |
vuejs | core | 781,899,907 | 3,264 | HcySunYang | Another workaround, you can remove the changes to the state, see https://codepen.io/hcysunyang/pen/wvoeOaa | 2021-02-19T07:50:02 | 2021-02-19T07:50:02 | {} | MEMBER |
vuejs | core | 782,787,902 | 1,473 | IamGiel | any update?
| 2021-02-21T03:10:29 | 2021-02-21T03:10:29 | {} | NONE |
vuejs | core | 783,839,741 | 3,280 | HcySunYang | Hi, thank you for your interest in Vue, but do you agree that this is a duplicate of #2970? | 2021-02-23T02:48:53 | 2021-02-23T02:48:53 | {} | MEMBER |
vuejs | core | 986,235,752 | 5,038 | ClassicOldSong | @kospl To be clear, I'm not refering to that specific comment but the fact that the whole discussion didn't make any change to Vue. | 2021-12-05T14:01:55 | 2021-12-05T14:01:55 | {} | NONE |
vuejs | core | 986,244,887 | 5,038 | ClassicOldSong | @kospl I tried, but you'll feel the same when you're getting trapped everywhere by the babysitter, talking to it but it teased you with `not skilled` and taped your mouth.
I'm really not saying that anyone should offence anyone discussing a problem on the public internet, but I was the first to be offenced by a word... | 2021-12-05T14:56:17 | 2021-12-05T14:56:17 | {
"-1": 1
} | NONE |
vuejs | core | 986,581,604 | 5,062 | posva | Set the new value inside an `onMounted()` hook if you want to change it client side. It is expected to have the same values on the server and client when doing SSR | 2021-12-06T09:13:39 | 2021-12-06T09:13:39 | {} | MEMBER |
vuejs | core | 986,747,066 | 5,063 | LinusBorg | Seems we have a bug here when bailing out of hydration because of a mismatch - the text content was updated, but the class attribute wasn't. | 2021-12-06T12:52:33 | 2021-12-06T12:52:33 | {} | MEMBER |
vuejs | core | 987,159,641 | 5,064 | ycw | element hooks are emitted in 'depth-first' fashion, which is the same order as unmount. In addition, directive hooks always come after its bounding element hooks tightly. The docs is correct but a lil bit confusing as the 'after being mounted' (被挂载后) in description text should refer to moment, not the parent element ho... | 2021-12-06T20:15:17 | 2021-12-06T20:15:17 | {} | NONE |
vuejs | core | 988,667,602 | 5,075 | posva | `$parent` cannot be typed because it depends on the runtime as a component could be the child of different components at runtime
`$root` being a type, I don't think you can extend it in your codebase to add properties 🤔
You could however add a custom global property (https://v3.vuejs.org/api/application-config.ht... | 2021-12-08T10:02:07 | 2021-12-08T10:02:07 | {} | MEMBER |
vuejs | core | 989,473,586 | 5,081 | purocean | > as a workaround
>
> ```js
> import { createApp, defineComponent, h } from "vue";
>
> const App = defineComponent({
> setup() {
> // return () => h("div", { innerHTML: undefined }, "a");
> return () => h("div", { innerHTML: undefined });
> }
> });
>
> createApp(App).mount("#app");
> ```
> ... | 2021-12-09T03:24:19 | 2021-12-09T03:24:19 | {} | NONE |
vuejs | core | 986,242,448 | 5,038 | kospl | @ClassicOldSong yeah, just try to be a professional, and polite when you discuss anything in public repository. We all can't agree with everything, but it's not a reason to offence or bully people on the internet. | 2021-12-05T14:44:05 | 2021-12-05T14:44:05 | {
"+1": 1
} | NONE |
vuejs | core | 986,234,735 | 5,038 | ClassicOldSong | @kospl Vue takes user's freedom of using `_` and `$` as their variable prefix away since Vue2 and not doing a thing about it in Vue3, even removed the warning that was present in Vue2. Similar things are happening in Vue in multiple aspects such as the previous version of `ref` proposal, which was trying to modify the ... | 2021-12-05T13:55:11 | 2021-12-05T14:56:55 | {} | NONE |
vuejs | core | 986,354,684 | 5,058 | caozhong1996 | I quite understand you wanna contribute for community, but I would say, maybe you can merged similar pr into one, it's not friendly for people who wanna search change history.😂
| 2021-12-06T01:17:42 | 2021-12-06T01:17:42 | {} | CONTRIBUTOR |
vuejs | core | 986,773,375 | 5,055 | aradalvand | > Redundant classes has no runtime implications and the performance overhead of deduping classes on every update is not worth it.
Understandable but then why does Vue already dedupe classes when not using class binding?
> It's also an edge where most of the time can be fixed by the end user.
Can you elaborate ... | 2021-12-06T13:24:51 | 2021-12-06T13:24:51 | {} | NONE |
vuejs | core | 988,919,844 | 3,989 | KenCorbettTruepic | If you wrap the slot in a div like this it doesn't complain anymore:
```html
<transition>
<div>
<slot />
</div>
</transition>
```
This feels like a hack but it at least gets rid of the warning. | 2021-12-08T15:34:07 | 2021-12-08T15:34:07 | {
"+1": 1
} | NONE |
vuejs | core | 984,033,739 | 4,294 | wheatjs | If you are using Vite, you can use this plugin https://github.com/wheatjs/vite-plugin-vue-type-imports as a patch until this is officially supported. | 2021-12-01T20:35:58 | 2021-12-01T20:35:58 | {
"+1": 56,
"eyes": 3,
"heart": 19,
"hooray": 6,
"rocket": 6
} | NONE |
vuejs | core | 985,522,213 | 5,030 | LinusBorg | `compile()` returns a function meant to be used as the render function of a component. it does not return a component object and can't be passed to `h()`.
```js
import { compile } from 'vue';
export default {
name: 'Compiled',
setup() {
return {};
},
render: compile('<div :class="$divclass">This... | 2021-12-03T13:29:26 | 2021-12-03T14:10:17 | {} | MEMBER |
vuejs | core | 985,580,217 | 4,294 | TylerOliver | @wheatjs , I gave the plugin a try before posting, but I couldn't get it working. Let me try again and see if I can at least post an issue with a basic recreation. I'm not sure if part of the issue had to do with running the compat build at the time, but that's no longer the case. I appreciate that you've made this th... | 2021-12-03T14:48:59 | 2021-12-03T21:04:34 | {} | NONE |
vuejs | core | 986,151,820 | 5,038 | caozhong1996 | Oh, sorry, my first impression is that someone intentionally rewrite builded api. But the focus is how to avoid conflicts, it does make sense. I came up with some ideas:
- If user-defined properties start with a underscore, we can give the name suggestion. eg console.log( '...not recommend' ). This is the simplest s... | 2021-12-05T02:02:20 | 2021-12-05T02:02:20 | {} | CONTRIBUTOR |
vuejs | core | 986,169,980 | 5,044 | caozhong1996 | This is likely intended, did you compare this change's effect on build output?🤔 | 2021-12-05T05:31:00 | 2021-12-05T05:40:42 | {} | CONTRIBUTOR |
vuejs | core | 986,419,234 | 5,050 | yyx990803 | Please group all typo fixes under this PR, thanks. | 2021-12-06T04:08:34 | 2021-12-06T04:08:34 | {
"+1": 1
} | MEMBER |
vuejs | core | 986,747,825 | 5,063 | LinusBorg | @loyep Even though yes, this is a bug - your usage of a computed here is wrong, too.
Looking at the console, you can see that it causes a hydration mismatch. | 2021-12-06T12:53:52 | 2021-12-06T12:54:10 | {} | MEMBER |
vuejs | core | 985,422,308 | 813 | SomeoneIsWorking | > @LastHeaven The attr fallthrough behavior was changed at [e1660f4](https://github.com/vuejs/vue-next/commit/e1660f4338fbf4d2a434e13193a58e00f844379b) for [vuejs/rfcs#137](https://github.com/vuejs/rfcs/pull/137). When you set `inheritAttrs: false` to MButton component, it will work as you expected.
Yes but this bre... | 2021-12-03T10:56:05 | 2021-12-03T10:57:14 | {} | NONE |
vuejs | core | 986,214,974 | 4,998 | LinusBorg | Not saying that there's no room to optimize SVG-related stuff, but I don't see how that's related to the specific issue here? | 2021-12-05T11:46:31 | 2021-12-05T14:19:32 | {} | MEMBER |
vuejs | core | 986,419,375 | 5,051 | yyx990803 | https://github.com/vuejs/vue-next/pull/5050#issuecomment-986419234 | 2021-12-06T04:08:48 | 2021-12-06T04:08:48 | {} | MEMBER |
vuejs | core | 986,419,497 | 5,054 | yyx990803 | https://github.com/vuejs/vue-next/pull/5050#issuecomment-986419234 | 2021-12-06T04:08:59 | 2021-12-06T04:08:59 | {} | MEMBER |
vuejs | core | 986,426,149 | 5,044 | yyx990803 | This is intended for tree-shaking. | 2021-12-06T04:22:20 | 2021-12-06T04:22:20 | {} | MEMBER |
vuejs | core | 986,426,963 | 4,964 | yyx990803 | I think we should patch it in VTU then, since this doesn't really make sense in normal applications. | 2021-12-06T04:24:10 | 2021-12-06T04:24:10 | {
"+1": 3
} | MEMBER |
vuejs | core | 988,809,070 | 4,344 | rhmkstk | Hi,
I am building a library with vue3 and vite, when i use the library if i use slot i got same issue, i tried the solutions in this thread but i can not fix the issue.
error: `Uncaught TypeError: Cannot read properties of null (reading 'isCE')`
My vite config.js:
```
import vue from '@vitejs/plugin-vue'
... | 2021-12-08T13:20:43 | 2021-12-08T13:22:30 | {
"+1": 15
} | NONE |
vuejs | core | 989,468,848 | 5,081 | caozhong1996 | as a workaround
````js
import { createApp, defineComponent, h } from "vue";
const App = defineComponent({
setup() {
// return () => h("div", { innerHTML: undefined }, "a");
return () => h("div", { innerHTML: undefined });
}
});
createApp(App).mount("#app");
````
In your case, `innerHTML` co... | 2021-12-09T03:14:09 | 2021-12-09T03:14:09 | {} | CONTRIBUTOR |
vuejs | core | 984,564,077 | 1,033 | dcy0701 | same problem @yyx990803 | 2021-12-02T12:02:21 | 2021-12-02T12:02:21 | {} | NONE |
vuejs | core | 985,547,554 | 5,030 | xlaussel | Thank you Linus for the help and sorry for the false issue | 2021-12-03T14:05:54 | 2021-12-03T14:05:54 | {} | NONE |
vuejs | core | 985,805,921 | 3,310 | LinusBorg | Closed as we use pnpm now. | 2021-12-03T20:26:15 | 2021-12-03T20:26:15 | {} | MEMBER |
vuejs | core | 986,178,235 | 5,036 | lidlanca | `binding.inject` not a good idea
exposing `provide/inject` indirectly via binding will be redundant, and just another non consistent way to do things.
additionally wouldn't binding the api force it into the bundle (tree shaking)
a directive hook already has access to the instance through the binding.
making ... | 2021-12-05T07:03:39 | 2021-12-05T07:04:38 | {} | CONTRIBUTOR |
vuejs | core | 986,229,278 | 5,038 | ClassicOldSong | Read it and got the feeling that the babysitter just won't let you take your own sip of milk. | 2021-12-05T13:20:36 | 2021-12-05T13:34:02 | {
"-1": 1
} | NONE |
vuejs | core | 986,233,647 | 5,038 | kospl | @ClassicOldSong so what exactly you found offensive in referenced comment? | 2021-12-05T13:48:34 | 2021-12-05T13:48:34 | {
"-1": 1
} | NONE |
vuejs | core | 986,236,118 | 4,998 | ClassicOldSong | I'm aware of that Vue does handle SVG differently: it has a built-in list of tags ~~and attributes~~ that are marked as SVG related. That's a very stubborn way of telling if a tag should be svg: once SVG adds some new attributes to it and it's not on the built-in list, users will have no way but dirty hacks to get it w... | 2021-12-05T14:04:21 | 2021-12-05T14:23:55 | {} | NONE |
vuejs | core | 986,559,117 | 4,397 | NoelDeMartin | In case this is useful for anyone, here's my current workaround:
MyComponent.d.ts
```ts
export interface IMyComponent {
doSomething(): void;
}
```
MyComponent.vue
```ts
<script setup lang="ts">
import type { IMyComponent } from './MyComponent';
defineExpose<IMyComponent>({
doSo... | 2021-12-06T08:47:33 | 2021-12-06T08:47:33 | {
"+1": 3,
"rocket": 2
} | CONTRIBUTOR |
vuejs | core | 986,753,258 | 5,062 | tedteddy | https://github.com/vuejs/vue-next/issues/5063
@posva | 2021-12-06T13:01:31 | 2021-12-06T13:01:31 | {} | NONE |
vuejs | core | 986,222,581 | 5,038 | kospl | Also, see discussion for version 2: https://github.com/vuejs/vue/issues/5879
And, [suggestion](https://github.com/vuejs/vue/issues/5879#issuecomment-468968269) from @Flamenco:
> I am probably going to get an ass whippin' for suggesting this, but I would like to see a refactoring of __ and $$ instead of _ and $ in... | 2021-12-05T12:35:03 | 2021-12-05T12:35:03 | {} | NONE |
vuejs | core | 986,231,371 | 5,038 | ClassicOldSong | @kospl No I'm not, but does it have anything to do with this issue? | 2021-12-05T13:33:35 | 2021-12-05T13:33:35 | {
"-1": 1
} | NONE |
vuejs | core | 986,218,709 | 4,998 | LinusBorg | Please open issues about these problems. They seem to be adjacent to the issue at hand, but not really related.
Also Vue deals fine with camelCase attributes in SVG, judging from a simple test, so you might have come across some edge case?
https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJ... | 2021-12-05T12:09:58 | 2021-12-05T14:19:24 | {
"+1": 1
} | MEMBER |
vuejs | core | 986,816,873 | 5,064 | posva | This could be also a documentation mismatch | 2021-12-06T14:16:49 | 2021-12-06T14:16:49 | {} | MEMBER |
vuejs | core | 988,854,116 | 5,071 | caozhong1996 | I'm not sure whether this is legal, it seems not been discussed, maybe involve directive's lifecycle.
不知道能不能增减绑定的指令，这似乎没有讨论过，可能涉及到指令的生命周期，不过你可以先暂时用一个指令传参代替。 | 2021-12-08T14:18:42 | 2021-12-08T14:18:42 | {} | CONTRIBUTOR |
vuejs | core | 982,765,166 | 5,024 | posva | Just use [`refTop` directly](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IEIgZnJvbSAnLi9CLnZ1ZSdcbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgcmVmVG9QID0gcmVmKClcbmNvbnN0IGRpc3BsYXkybmQgPSByZWYoZmFsc2UpXG48L3NjcmlwdD5cblxuPHRlbXBsYXRlPlxuICA8QiA6cj1cInJlZlRvUFwiPjwvQj5cbiAgPEIgdi1pZj1cImRp... | 2021-11-30T15:49:27 | 2021-11-30T15:49:27 | {} | MEMBER |
vuejs | core | 982,870,430 | 4,994 | simlevesque | @yyx990803 @caozhong1996
This works: https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cCBsYW5nPVwidHNcIj5cbmltcG9ydCB7IHJlZiwgdG9SZWZzIH0gZnJvbSAndnVlJ1xuXG5jb25zdCBwcm9wcyA9IGRlZmluZVByb3BzKHtcbiAgXHRtc2c6IHtcbiAgICAgIHR5cGU6IFN0cmluZ1xuICAgIH1cbn0pXG5jb25zdCB7IG1zZyB9ID0gdG9SZWZzKHByb3BzKTtcbjwvc2NyaXB0Plxu... | 2021-11-30T17:44:53 | 2021-11-30T18:31:10 | {} | CONTRIBUTOR |
vuejs | core | 986,055,852 | 5,038 | ClassicOldSong | As Vue continues to develop, it might accidently take over what users used as their variable names and then break things.
What's more, users have the right to use anything they want as their variable names, at least get a warning if accidently encountered one built-in keyword that might break things. | 2021-12-04T16:41:04 | 2021-12-04T16:41:04 | {} | NONE |
vuejs | core | 986,068,208 | 5,038 | posva | We could indeed warn during compilation so the user is aware they need to change the name of the variable | 2021-12-04T18:02:47 | 2021-12-04T18:03:39 | {} | MEMBER |
vuejs | core | 986,072,129 | 5,038 | Justineo | Ideally we should rewrite conflicted identifiers to unique ones, as our internal identifiers may change over time thus accidentally break user code which used to work. But I think the chance of conflicts are quite low ATM. | 2021-12-04T18:27:47 | 2021-12-04T18:27:47 | {} | MEMBER |
vuejs | core | 802,834,456 | 3,450 | zhangenming | 
make sense, but... Is it a little troublesome?
A lot of users don't know this, like me
A NEW USE CASE
![image](https://user-images.githubusercontent.com/21235555/144733964-01ad80e4-38b0-4294-93cf-8b55f... | 2021-03-19T13:31:03 | 2021-12-05T04:47:22 | {} | CONTRIBUTOR |
vuejs | core | 986,419,921 | 5,049 | yyx990803 | Thanks, this has been removed by another commit. | 2021-12-06T04:09:42 | 2021-12-06T04:09:42 | {
"+1": 1
} | MEMBER |
vuejs | core | 986,484,162 | 5,059 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2021-12-06T06:43:01 | 2021-12-06T06:43:01 | {} | CONTRIBUTOR |
vuejs | core | 986,499,235 | 5,060 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2021-12-06T07:12:27 | 2021-12-06T07:12:27 | {} | CONTRIBUTOR |
vuejs | core | 986,555,534 | 813 | Chrisx0385 | > In v3 all `v-on` listeners will fallthrough to child component root by default - which means it's no longer necessary to manually re-emit the `click` event. You can simply remove your click listener in the child instead of using `inheritAttrs: false` (which disables fallthrough for other attributes, e.g. `class`)
... | 2021-12-06T08:42:14 | 2021-12-06T08:42:14 | {
"+1": 6
} | NONE |
vuejs | core | 986,691,957 | 5,063 | loyep | @posva | 2021-12-06T11:33:23 | 2021-12-06T11:33:23 | {} | NONE |
vuejs | core | 988,556,842 | 5,075 | CarterLi | `$root` and `$parent` are generally typed as `ComponentPublicInstance | null`, which makes them almost unusable in vue template. Even `any` can be a better option than `ComponentPublicInstance | null` like what we did for `$el`
| 2021-12-08T07:12:04 | 2021-12-08T07:13:13 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 984,895,380 | 4,397 | aradalvand | Any updates on this one?
This would genuinely improve the developer experience.
This issue is also the fourth most upvoted open issue in this repo. | 2021-12-02T18:39:31 | 2021-12-02T18:44:44 | {
"+1": 16
} | NONE |
vuejs | core | 986,082,408 | 5,040 | posva | Hello, make sure to always provide a reproduction that follows the instructions at https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro.
Open a new issue with a reproduction that follows those instructions if you manage to create a boiled down reproduction. | 2021-12-04T19:41:14 | 2021-12-04T19:41:14 | {} | MEMBER |
vuejs | core | 986,420,800 | 5,056 | yyx990803 | It is intentional. | 2021-12-06T04:11:21 | 2021-12-06T04:11:21 | {} | MEMBER |
vuejs | core | 986,808,537 | 4,397 | DannyFeliz | This should be now fixed by @NoelDeMartin here #5035 | 2021-12-06T14:07:49 | 2021-12-06T14:07:49 | {} | NONE |
vuejs | core | 986,842,121 | 4,397 | NoelDeMartin | It is a workaround, but I'm not sure if it's temporary or the only viable solution with the current architecture. As far as I understand, `.vue` files are declared with [a generic shim](https://github.com/vitejs/vite/blob/main/packages/create-vite/template-vue-ts/src/env.d.ts), so you're already getting the same type f... | 2021-12-06T14:45:19 | 2021-12-06T14:45:19 | {} | CONTRIBUTOR |
vuejs | core | 988,552,457 | 5,072 | LinusBorg | You are using it wrong. You use Suspense *inside of* a component with async setup, which is wrong.
You should be using a component with async setup *as a child of* Suspense. | 2021-12-08T07:03:23 | 2021-12-08T07:03:23 | {} | MEMBER |
vuejs | core | 984,031,491 | 4,294 | TylerOliver | To follow up on @cdvillard 's commentary -- In a world where there are many packages interacting with each other, such as Jest testing and Storybook's stories, being able to maintain a reusable interface that can be imported in our .vue components, and our other .ts files, makes a massive difference in our ability to a... | 2021-12-01T20:32:40 | 2021-12-01T20:32:40 | {
"+1": 74,
"heart": 6
} | NONE |
vuejs | core | 985,976,327 | 5,034 | yuwu9145 | change to `const text = ref('"something"')` | 2021-12-04T06:09:00 | 2021-12-04T06:09:00 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 986,107,103 | 5,041 | adamreisnz | Alright thanks, if you can find the open issue so that I (or anyone finding this in the future) can track the progress for it that would be much appreciated. | 2021-12-04T23:11:26 | 2021-12-04T23:11:26 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.