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 | 986,419,652 | 5,057 | yyx990803 | https://github.com/vuejs/vue-next/pull/5050#issuecomment-986419234 | 2021-12-06T04:09:15 | 2021-12-06T04:09:15 | {} | MEMBER |
vuejs | core | 986,423,394 | 4,883 | yyx990803 | Closing as stale. If you can provide proper reproduction, please open a new issue. | 2021-12-06T04:16:31 | 2021-12-06T04:16:31 | {} | MEMBER |
vuejs | core | 985,978,832 | 5,034 | d602221169 | > change to `const text = ref('"something"')`
thanks for your answer，according for your tips, i solved the problem | 2021-12-04T06:34:41 | 2021-12-04T06:34:41 | {} | NONE |
vuejs | core | 986,421,067 | 5,058 | yyx990803 | This is intentionally written this way to highlight the logic flow. | 2021-12-06T04:11:53 | 2021-12-06T04:11:53 | {} | MEMBER |
vuejs | core | 987,813,284 | 4,817 | gfordinal | Same problem here.
Seems to appear on `v-for` and dynamic components `<component :is="" />`
@tcstory Could you find a solution?
| 2021-12-07T10:57:33 | 2021-12-07T10:57:33 | {} | NONE |
vuejs | core | 986,205,611 | 5,047 | 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-05T10:38:27 | 2021-12-05T10:38:27 | {} | CONTRIBUTOR |
vuejs | core | 986,216,105 | 4,998 | ClassicOldSong | > 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?
You're not realizing that tags appear in html can have and do have case sensitive attributes and tag names, which vue have completely no way to deal with.
Not mentioning XML namespaces which... | 2021-12-05T11:54:16 | 2021-12-05T14:19:28 | {} | NONE |
vuejs | core | 986,438,390 | 4,950 | yuwu9145 | FYI: built-in components still have type inference issue in `defineComponent`
| 2021-12-06T04:57:14 | 2021-12-06T04:58:10 | {} | CONTRIBUTOR |
vuejs | core | 986,514,556 | 5,061 | everettmorgan | Welp, I just added the custom definition to the shim.d.ts file and all is well. Closing issue since this is a fine workaround. | 2021-12-06T07:41:00 | 2021-12-06T07:41:00 | {} | NONE |
vuejs | core | 989,407,236 | 5,080 | caozhong1996 | ~~May be a bit better, cach `length`😃~~
~~
It do not make much difference whether `for `or `while`, it has been optimized by browser.
| 2021-12-09T01:38:40 | 2021-12-09T02:29:40 | {} | CONTRIBUTOR |
vuejs | core | 983,199,616 | 5,024 | ubbcou | @rgaudy You just need to define `refTop` and use refTop directly: [example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IEIgZnJvbSAnLi9CLnZ1ZSdcbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgY291bnRlciA9IHJlZigwKVxuY29uc3QgcmVmVG9QID0gcmVmKCkgLy8gdGhlIGxpbmVcbjwvc2NyaXB0PlxuXG48dGVtcGxhdGU+X... | 2021-12-01T01:37:28 | 2021-12-01T01:37:28 | {} | NONE |
vuejs | core | 985,977,873 | 5,034 | caozhong1996 | Duplicated #4880, it's invalid `content` without quotation.
| 2021-12-04T06:24:21 | 2021-12-04T06:24:21 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 986,821,121 | 4,397 | aradalvand | But this is meant to be a temporary workaround, is that right?
Ideally the language server should be able to detect the type of the argument passed to `defineExpose` and add it to the component type, without the developer having to extract, declare, and export+import a separate interface | 2021-12-06T14:21:29 | 2021-12-06T14:23:04 | {
"+1": 2
} | NONE |
vuejs | core | 986,805,273 | 5,064 | edison1105 | > 自定义指令mounted：在绑定元素的父组件被挂载后调用
父组件挂载后，并不是指父组件的 mounted 执行之后。这里是有区别的。 | 2021-12-06T14:04:00 | 2021-12-06T14:44:01 | {} | MEMBER |
vuejs | core | 987,498,061 | 5,064 | sakura-he | 经测试,在自定义指令的mounted钩子中可以获取到父组件的dom元素;可以证明钩子是在父组件挂在后执行的; | 2021-12-07T02:01:30 | 2021-12-07T02:01:30 | {} | NONE |
vuejs | core | 989,031,432 | 5,077 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/2279 | 2021-12-08T17:42:40 | 2021-12-08T17:42:40 | {} | MEMBER |
vuejs | core | 986,434,037 | 5,050 | sudongyuer | >
Ok,i will do it right now, thanks big You 👻 | 2021-12-06T04:42:34 | 2021-12-06T04:42:34 | {} | CONTRIBUTOR |
vuejs | core | 987,488,258 | 5,064 | sakura-he | 谢谢大佬们的答疑,是我理解错了 | 2021-12-07T01:38:07 | 2021-12-07T01:38:07 | {} | NONE |
vuejs | core | 987,977,510 | 5,070 | posva | It's because you used a non existant method `resetOptions`. It works [if you use the right method](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBsYW5nPVwidHNcIj5cbmltcG9ydCB7IGRlZmluZUNvbXBvbmVudCwgcmVhY3RpdmUgfSBmcm9tICd2dWUnXG4gIFxudHlwZSBGcm9udGVuZE9wdGlvbnMgPSB7bGFiZWw6IHN0cmluZzsgdmFsdWU6IHN0cmluZzsgfVxuICBcbm... | 2021-12-07T14:28:58 | 2021-12-07T14:28:58 | {} | MEMBER |
vuejs | core | 986,053,236 | 5,038 | caozhong1996 | Who really needs it? I think it's meaningless, this is not worth the effort🤔 | 2021-12-04T16:22:35 | 2021-12-04T16:26:03 | {
"-1": 2
} | CONTRIBUTOR |
vuejs | core | 986,082,288 | 5,038 | posva | I think that's why they are all prepended with `_`: to avoid conflicts with user-defined properties. But yeah, they could be rewritten too | 2021-12-04T19:40:13 | 2021-12-04T19:40:13 | {} | MEMBER |
vuejs | core | 986,097,111 | 5,041 | LinusBorg | they are missing just like declared props are missing from $attrs.
We have an open issue about this already where we noted that we might consider a way to access cust event listeners like you can access props. Can't find it right now though.
For now, you can declare the listener as a prop with on* prefix (which i... | 2021-12-04T21:41:12 | 2021-12-04T21:42:13 | {} | MEMBER |
vuejs | core | 986,750,129 | 5,063 | loyep | Yes, I know. Only in this way can we reproduce this problem quickly. | 2021-12-06T12:57:05 | 2021-12-06T12:57:05 | {} | NONE |
vuejs | core | 987,717,683 | 5,068 | Niputi | duplicate of https://github.com/vuejs/vue-next/issues/4294 | 2021-12-07T09:10:31 | 2021-12-07T09:10:31 | {} | NONE |
vuejs | core | 987,868,059 | 5,048 | caozhong1996 | Such cases are extremely rare, you can expect no one will rely on it, so this change won't cause problems.
For me, I hope readonly is highest priority, because I don't want to memorize summary table.
| 2021-12-07T12:11:20 | 2021-12-07T12:11:20 | {} | CONTRIBUTOR |
vuejs | core | 982,770,461 | 5,024 | rgaudy | Sorry but here's [another example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IEIgZnJvbSAnLi9CLnZ1ZSdcbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgY291bnRlciA9IHJlZigwKVxuPC9zY3JpcHQ+XG5cbjx0ZW1wbGF0ZT5cbiAgPEIgOnI9XCIkcmVmcy5yZWZUb1BcIj48L0I+XG5cbiAgPGJyPlxuICA8YnV0dG9uIEBjbGljaz1cImNvdW... | 2021-11-30T15:55:10 | 2021-11-30T15:56:43 | {} | NONE |
vuejs | core | 983,058,954 | 2,513 | zetokore | For anyone else attempting @zauan's fix in Vite, here's what I needed to do-
1. Update /node_modules/@vue/runtime-dom/dist/runtime-dom.esm-bundler.js as per his gist file
2. Clear out all files from /node_modules/.vite
3. npm run dev | 2021-11-30T22:01:32 | 2021-11-30T22:01:32 | {} | NONE |
vuejs | core | 985,589,275 | 3,399 | aradalvand | Any updates on this? | 2021-12-03T15:00:32 | 2021-12-03T15:00:32 | {
"+1": 32
} | NONE |
vuejs | core | 986,230,836 | 5,038 | kospl | @ClassicOldSong are you a socialist? | 2021-12-05T13:30:08 | 2021-12-05T13:30:08 | {
"-1": 1
} | NONE |
vuejs | core | 986,374,192 | 5,058 | sudongyuer | > 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.😂
😂，because i don't sure which can be merge,so i split it. | 2021-12-06T02:09:26 | 2021-12-06T02:09:26 | {} | CONTRIBUTOR |
vuejs | core | 988,178,650 | 5,069 | leopiccionia | It won't work. If, for example, `globalThis` is not defined, it will throw a `ReferenceError`. | 2021-12-07T18:44:10 | 2021-12-07T18:44:10 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 984,311,639 | 4,994 | caozhong1996 | `DefineProps` does not exist at runtime, so just don't do this.🙃
````js
const { msg } = toRefs(defineProps({
msg: {
type: String
}
}))
```` | 2021-12-02T05:42:55 | 2021-12-02T06:00:46 | {
"+1": 7,
"-1": 2,
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 985,166,091 | 906 | kevin3592 | I was having the same issue, and the comments didn`t fix for me, however I fixed this by making sure that all the pages have only 1 root element. Seems like the issue is between the transition element, and the child component having no wrapper at all or multiple root elements at the same time.
````
<template>
... | 2021-12-03T02:36:24 | 2021-12-03T02:36:24 | {} | NONE |
vuejs | core | 986,036,998 | 4,998 | ClassicOldSong | @posva That's not the case. In SVG elements, not only the attributes are case sensitive, even the tags them selves are. This is a fundamental problem with Vue and that's a reason why I choose to create my own framework. | 2021-12-04T14:30:39 | 2021-12-05T14:19:36 | {} | NONE |
vuejs | core | 986,422,446 | 5,055 | yyx990803 | This is expected behavior. Redundant classes has no runtime implications and the performance overhead of deduping classes on every update is not worth it. It's also an edge where most of the time can be fixed by the end user. | 2021-12-06T04:14:31 | 2021-12-06T04:15:19 | {} | MEMBER |
vuejs | core | 986,754,081 | 5,063 | loyep | > LinusBorg
Not only class, but also style attributes | 2021-12-06T13:02:26 | 2021-12-06T13:02:26 | {} | NONE |
vuejs | core | 986,891,873 | 5,064 | caozhong1996 | 
兄弟，debugger一下发现好像没毛病的，父组件的mounted的console后执行好像是因为父组件mounted注册的钩子在自定义指令钩子后面，但确实是父组件先mounted再自定义指令mounted。可以用`document.getElementsByClassName('xxx')`获取dom来验证。 | 2021-12-06T15:37:42 | 2021-12-06T15:37:42 | {} | CONTRIBUTOR |
vuejs | core | 988,686,399 | 5,075 | CarterLi | > In both scenarios, you will have to manually type your root app as there is no way to directly infer the global type of $root in vue from a createApp() call.
I was aware of it. In addition, there can be multiple `createApp`s in one project.
`$el` should have been typed as `Node`, but we type `$el` as `any` beca... | 2021-12-08T10:26:55 | 2021-12-08T10:33:12 | {} | CONTRIBUTOR |
vuejs | core | 823,738,442 | 3,638 | HcySunYang | It should be a common situation to include template ref in reactive object, so I think @edison1105 's PR is reasonable, of course, this has additional runtime overhead. There are still other situations here, such as including host objects(e.g. `window`) or components in the reactive object, but they are not as common a... | 2021-04-21T02:50:11 | 2021-04-21T02:50:25 | {} | MEMBER |
vuejs | core | 820,921,910 | 3,579 | hyf0 | digging | 2021-04-16T05:42:12 | 2021-04-16T05:42:12 | {} | CONTRIBUTOR |
vuejs | core | 822,686,527 | 3,627 | LongTengDao | `resolveDynamicComponent` will treat custom element tag as-is, only if the tag is not found in components.
This works right by `isCustomElement` API:
```js
customElement.define('aa-bb', class extends HTMLElement {
constructor () {
super();
this.innerHTML = 'element';
}
});
const a... | 2021-04-19T18:35:39 | 2021-04-19T18:36:02 | {} | CONTRIBUTOR |
vuejs | core | 818,865,899 | 3,596 | posva | @phanan I think your input would be valuable here | 2021-04-13T16:19:29 | 2021-04-13T16:19:29 | {} | MEMBER |
vuejs | core | 818,942,330 | 3,596 | phanan | Hmm, TBH I'm not sure why this 1.x behavior was revived in v3, but I still tend to agree with 4-year-ago me 😄 that this warning isn't extremely helpful. Again, as the original v2 issue author said, there are frameworks/libraries/CMSes that generate inline `value` attributes, which would cause this warning to be thrown... | 2021-04-13T18:01:37 | 2021-04-13T18:01:37 | {} | MEMBER |
vuejs | core | 821,325,447 | 3,619 | posva | The fix could be similar to the one for https://github.com/vuejs/vue-next/issues/1352 | 2021-04-16T17:26:10 | 2021-04-16T17:26:10 | {} | MEMBER |
vuejs | core | 822,240,254 | 3,618 | rashfael | I understand the underlying problem and the principle of ref/reactive, but options api users do not call the reactivity api explictly. The template works if the array comes out of `data`, but does not work if the array comes out of a computed prop.
This also used to work in vue2 and for it to stop working in the opti... | 2021-04-19T07:28:44 | 2021-04-19T07:28:44 | {} | NONE |
vuejs | core | 818,599,157 | 3,593 | Edge00 | @posva This is a feature requests. Should i modidy the descriptions above? | 2021-04-13T09:37:54 | 2021-04-13T09:37:54 | {} | NONE |
vuejs | core | 818,609,293 | 3,593 | posva | Asking us to do a PR in another repository is not a feature request | 2021-04-13T09:54:07 | 2021-04-13T09:54:07 | {} | MEMBER |
vuejs | core | 822,131,949 | 3,618 | HcySunYang | In Vue3, this should be the expected behavior, and it has nothing to do with the computed. Let's say you have a raw array and a ref:
```js
const rawArr = [{ a: 1 }, { b: 2 }]
const item = ref(null)
item.value = rawArr[0]
console.log(item.value === rawArr[0]) // false, should be expected
```
| 2021-04-19T02:55:52 | 2021-04-19T02:55:52 | {} | MEMBER |
vuejs | core | 822,253,044 | 3,618 | HcySunYang | My initial point is that it should be the user’s responsibility, but I realized that this might be a breaking change, it works in vue2 https://jsfiddle.net/HcySunYang/5hqt3su6/2/. | 2021-04-19T07:48:55 | 2021-04-19T07:48:55 | {} | MEMBER |
vuejs | core | 822,948,561 | 3,631 | Justineo | We do want shorter URLs but this change will break all generated links that were already shared in discussions, bug reports, etc. | 2021-04-20T03:35:19 | 2021-04-20T03:35:19 | {} | MEMBER |
vuejs | core | 818,646,903 | 3,595 | kshq1996 | 图片如下：
As shown in the pic above, you can see the problematic component(`<MyComponent>`) and the cause of the error(`failed to resol... | 2021-04-22T03:03:40 | 2021-04-22T03:03:40 | {} | MEMBER |
vuejs | core | 824,551,462 | 3,647 | HcySunYang | I get your points now, but it will return `undefined` only if an effect has the `scheduler` option and it is **inactive**. But here is [another issue](https://github.com/vuejs/vue-next/issues/3099) discussing whether an effect should always return non-undefined when it is inactive, so we don't need to do anything for n... | 2021-04-22T05:33:53 | 2021-04-22T05:34:20 | {
"+1": 1
} | MEMBER |
vuejs | core | 824,703,067 | 3,649 | HcySunYang | Yes, you are using the wrong way, `async setup` can only be used in SSR, or must be used in CSR with the `Suspense` component, see https://codesandbox.io/s/vue-async-setup-forked-31tyl. You are not the only one who has encountered similar confusion, I think we can improve the error report.
| 2021-04-22T09:53:27 | 2021-04-22T09:53:27 | {} | MEMBER |
vuejs | core | 824,715,039 | 3,649 | pdsuwwz | > Yes, you are using the wrong way, `async setup` can only be used in SSR, or must be used in CSR with the `Suspense` component, see https://codesandbox.io/s/vue-async-setup-forked-31tyl. You are not the only one who has encountered similar confusion, I think we can improve the error report.
Thanks! @HcySunYang , Yo... | 2021-04-22T10:11:54 | 2021-04-22T10:24:33 | {} | NONE |
vuejs | core | 818,397,963 | 1,598 | HcySunYang | We now have `useContext` https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/apiSetupHelpers.ts#L59-L65 | 2021-04-13T03:09:06 | 2021-04-13T03:09:06 | {} | MEMBER |
vuejs | core | 819,273,321 | 3,596 | phanan | AFAIU there's no warning for `:value`, which is expected right? But I'd tend to agree that `:value` not overriding `value` sounds weird. Maybe @yyx990803 can shed a light on both topics here? | 2021-04-14T06:47:12 | 2021-04-14T06:47:23 | {} | MEMBER |
vuejs | core | 819,277,711 | 3,596 | posva | Now that I read the comment again, I was more thinking of a `:value` with a `v-model` throwing a warning instead of any value attribute with a v-model | 2021-04-14T06:55:59 | 2021-04-14T06:55:59 | {} | MEMBER |
vuejs | core | 822,972,445 | 3,636 | HcySunYang | Open the link you provided, edit `Home.jsx`, you can see that it can be hot updated. | 2021-04-20T04:54:46 | 2021-04-20T04:54:46 | {} | MEMBER |
vuejs | core | 823,664,646 | 3,638 | trailskr | Official documentation uses simple refs for this purpose:
https://v3.vuejs.org/guide/composition-api-template-refs.html#template-refs
@Sociosarbis When using refs on HTMLElement or anything else, that is not common data container it will not be replaced by proxy, because code checks concrete type of that value. Tha... | 2021-04-20T23:27:04 | 2021-04-20T23:27:46 | {} | NONE |
vuejs | core | 824,647,884 | 3,590 | fangbinwei | I think it's similar to https://github.com/vuejs/vue-next/pull/2943 | 2021-04-22T08:28:15 | 2021-04-22T08:28:15 | {} | NONE |
vuejs | core | 818,595,262 | 3,593 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js). | 2021-04-13T09:31:47 | 2021-04-13T09:31:47 | {} | MEMBER |
vuejs | core | 818,679,227 | 3,595 | edison1105 | Your `places` are misspelled.
你的 places 拼错了，保证所有地方都拼写对，应该能正常工作。 | 2021-04-13T12:00:00 | 2021-04-13T12:01:00 | {} | MEMBER |
vuejs | core | 818,955,982 | 3,596 | posva | what about `:value` and [this proposal](https://github.com/vuejs/vue-next/issues/3596#issuecomment-818856369) | 2021-04-13T18:20:20 | 2021-04-13T18:20:20 | {} | MEMBER |
vuejs | core | 819,634,963 | 3,596 | nfplee | I personally feel that `:value` should override the `value` attribute (to be consistent with `v-model`). But I agree it makes sense to throw a warning if `:value` is used with `v-model`. | 2021-04-14T16:05:14 | 2021-04-14T16:05:14 | {} | NONE |
vuejs | core | 823,597,696 | 3,622 | Lucien950 | pog | 2021-04-20T21:00:50 | 2021-04-20T21:00:50 | {} | NONE |
vuejs | core | 818,413,970 | 3,566 | Justineo | @HcySunYang Yeah I believe both issues rely on options being merged correctly. | 2021-04-13T04:02:07 | 2021-04-13T04:02:07 | {} | MEMBER |
vuejs | core | 820,393,716 | 3,613 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js).
---
Since it's teleported somewhere else, that would... | 2021-04-15T12:45:24 | 2021-04-15T12:45:24 | {} | MEMBER |
vuejs | core | 821,863,400 | 3,467 | frandiox | I'm also having issue with `stream` dependency. The thing is, I'm only importing `renderToString`, not `renderToStream` but, since the production build of `@vue/server-renderer` is CJS, Rollup cannot do the tree shake.
Perhaps just providing an ESM build could work? | 2021-04-17T18:06:13 | 2021-04-17T18:06:13 | {} | NONE |
vuejs | core | 821,865,821 | 3,111 | frandiox | I'm trying to use `renderToString` in Cloudflare Workers and right now it only works because Webpack adds some magic to mock the `stream` dependency. It would be great to have ESM build for this so we can just import `renderToString` without bringing the whole package. | 2021-04-17T18:21:35 | 2021-04-17T18:21:35 | {} | NONE |
vuejs | core | 823,339,212 | 3,631 | Justineo | > as I mentioned in the issue #3630, `lzutf8.decompress` can also decompress Base64 generated by btoa, so old sfc-url works too.
Oh, I totally missed that. Thank you for your explanation! I have no other questions. | 2021-04-20T14:52:11 | 2021-04-20T14:52:11 | {} | MEMBER |
vuejs | core | 823,571,661 | 3,107 | geekox86 | Greetings. Sorry for commenting on a closed issue. I need to access the raw expression passed to the directive in Vue 3. Is there a way to do so? I need to process it. | 2021-04-20T20:15:58 | 2021-04-20T20:15:58 | {} | NONE |
vuejs | core | 823,957,554 | 2,027 | lvsong77 | > vue3 中，这个是devtools 6.0.0 beta 2打印的，我把devtools关闭，这个waring就消失了
same situation with u, it's OK when I closed devtool. | 2021-04-21T10:30:34 | 2021-04-21T10:30:34 | {} | NONE |
vuejs | core | 824,287,012 | 2,064 | gaetandezeiraud | Same here. And the @skirtles-code solution don't work for me. | 2021-04-21T18:59:26 | 2021-04-21T18:59:26 | {} | NONE |
vuejs | core | 820,277,060 | 3,609 | HcySunYang | 1. Do not modify props because it is read-only. If you use the dev build of Vue, you will get a warning. see the [One Way Data Flow](https://v3.vuejs.org/guide/component-props.html#one-way-data-flow)
2. You have completely misunderstood the meaning of slots, I recommend you to read the documentation first:
- [Compo... | 2021-04-15T09:28:01 | 2021-04-15T09:28:01 | {} | MEMBER |
vuejs | core | 820,365,962 | 3,612 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/3610 | 2021-04-15T11:56:36 | 2021-04-15T11:56:36 | {} | MEMBER |
vuejs | core | 823,404,920 | 3,638 | Sociosarbis | I wonder is "is dom node ?" is a good criteria to determine an object can be traversed or not.
As DOM Node is nothing special than other normal objects and the PR above is made in runtime-core package which I think should involve environment specific code as less as possible and that's why there's a runtime-dom pack... | 2021-04-20T16:06:18 | 2021-04-20T16:06:18 | {
"+1": 1
} | NONE |
vuejs | core | 818,594,480 | 3,566 | posva | @HcySunYang I think it's a bit different.
#2119 was initially about being able to retrieve `beforeRouteEnter()` and other custom options added by the router when the user adds them through `mixins`. Because they are custom, we would also need a custom merge strategy.
So, IMO solving this issue doesn't require sol... | 2021-04-13T09:30:29 | 2021-04-13T09:30:29 | {} | MEMBER |
vuejs | core | 818,601,381 | 3,594 | CHOYSEN | I'm not sure if it was the HMR, because from the response it worked.
If I modify the placeholders of these two components:
```js
import { createHotContext as __vite__createHotContext } from "/@vite/client";import.meta.hot = __vite__createHotContext("/src/App.vue");const _sfc_main = {}
import { resolveComponent as... | 2021-04-13T09:41:30 | 2021-04-13T09:45:49 | {} | CONTRIBUTOR |
vuejs | core | 818,837,053 | 3,595 | kshq1996 | > Your `places` are misspelled.
> 你的 places 拼错了，保证所有地方都拼写对，应该能正常工作。
WTF，Thanks I got it， | 2021-04-13T15:41:02 | 2021-04-13T15:41:02 | {} | NONE |
vuejs | core | 819,213,380 | 2,839 | HcySunYang | Finally, I gave a more appropriate solution https://github.com/vuejs/vue-next/pull/3600 | 2021-04-14T04:08:37 | 2021-04-14T04:08:37 | {
"+1": 1
} | MEMBER |
vuejs | core | 818,856,369 | 3,596 | nfplee | What about when using `:value` alongside the `value` attribute? From my understanding `v-model` is shorthand for `:value="foo" @input="foo = $event.target.value"`. However when using `:value` it doesn't seem to override the `value` attribute unlike `v-model`. See the following for an example:
https://jsfiddle.net/s2... | 2021-04-13T16:06:31 | 2021-04-14T16:05:32 | {} | NONE |
vuejs | core | 820,336,186 | 3,609 | manusis | Thanks @HcySunYang @Sociosarbis and sorry for the naive question. We come from AngularJS background and are new to Vue.
Our use case is very simple, we want to use the component inner html if available as a template, otherwise use the template provided in component options. Tried multiple things but nothing worked. ... | 2021-04-15T11:03:13 | 2021-04-15T11:04:30 | {} | NONE |
vuejs | core | 820,925,456 | 3,541 | HcySunYang | Calling `shift/unshift...`on the proxy array is an extremely performance-consuming operation https://jsbench.me/n5knjtmjlz/1 | 2021-04-16T05:50:33 | 2021-04-16T05:50:33 | {
"eyes": 1
} | MEMBER |
vuejs | core | 821,587,527 | 2,863 | theoribeiro | Thanks for the effort @chrislone @yyx990803. This issue was closed by your PR, however, the original repro still doesn't work even after updating to 3.0.11.
Has this been published? | 2021-04-16T22:04:47 | 2021-04-16T22:04:47 | {
"+1": 3
} | NONE |
vuejs | core | 823,702,859 | 3,638 | edison1105 | Before I submit the PR, I have realized that using `Node` is inappropriate. When I saw the code below, I still submitted a PR.
https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/components/Teleport.ts#L29
```javascript
const isTargetSVG = (target: RendererElement): boolean =>
typeof SVGElem... | 2021-04-21T01:09:04 | 2021-04-21T01:09:04 | {} | MEMBER |
vuejs | core | 824,462,248 | 3,643 | edison1105 | another workaround
```diff
@click.shift.stop="callback('click + shift')"
-@click="callback('click')"
+@click.exact="callback('click')"
```
see https://v3.vuejs.org/guide/events.html#exact-modifier | 2021-04-22T01:05:18 | 2021-04-22T01:05:18 | {} | MEMBER |
vuejs | core | 824,498,277 | 3,643 | HcySunYang | Duplicate of https://github.com/vuejs/vue-next/issues/916
Modifier `.stop` is equivalent to `e.stopPropagation()`, not `e.stopImmediatePropagation()`. But yep, you need to manually execute the `e.stopImmediatePropagation()` function | 2021-04-22T02:46:51 | 2021-04-22T02:46:51 | {} | MEMBER |
vuejs | core | 824,544,682 | 3,647 | hyf0 | > Please double-check the reproduction you provided, it cannot reproduce the problem you described.
`@vue/reactivity` does't export `createReactiveEffect` , but `effect`(exported) return result of `createReactiveEffect` finally, so they have same problem cause by `createReactiveEffect`.
so [Reproduction link](https... | 2021-04-22T05:16:08 | 2021-04-22T05:16:08 | {} | CONTRIBUTOR |
vuejs | core | 818,669,925 | 3,595 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js). | 2021-04-13T11:42:24 | 2021-04-13T11:42:24 | {} | MEMBER |
vuejs | core | 818,865,420 | 3,598 | posva | The cast operator in TS is `as` and it replaces the version you were using a long time ago. Precisely to avoid ambiguity: https://github.com/Microsoft/TypeScript/wiki/What's-new-in-TypeScript#new-tsx-file-extension-and-as-operator | 2021-04-13T16:18:50 | 2021-04-13T16:18:50 | {
"heart": 1
} | MEMBER |
vuejs | core | 820,938,647 | 3,616 | Justineo | Thank you for reporting this but please provide a runnable reproduction as instructed by our issue helper. If it cannot be reproduced with our SFC playground or CodeSandbox, please create a GitHub repo for it and make sure the reproduction you provide is minimal (without unnecessary code or dependencies). Read more [he... | 2021-04-16T06:19:42 | 2021-04-16T06:19:42 | {} | MEMBER |
vuejs | core | 820,102,550 | 3,606 | HcySunYang | Regarding the type of TSX supported by `jsx-next`, you should submit the issue to the correct repo. BTW, you need to provide as detailed information as possible, preferably with a demo. | 2021-04-15T05:16:53 | 2021-04-15T05:16:53 | {} | MEMBER |
vuejs | core | 820,249,313 | 3,607 | HcySunYang | @pikax will give a new PR | 2021-04-15T08:56:42 | 2021-04-15T08:56:42 | {} | MEMBER |
vuejs | core | 820,361,532 | 3,611 | posva | Open the issue on echarts repository | 2021-04-15T11:48:45 | 2021-04-15T11:48:45 | {} | MEMBER |
vuejs | core | 820,919,589 | 3,077 | hyf0 | same problem.
```ts
foo: {
type: String,
validator: (value): value is 'bar' => value === 'bar'
}
// expected:
props.foo // => 'bar'
// now:
props.foo // => String | undefined
```
imagine world:
```ts
propType.string = (value): value is string => typeof value === 'string'
propTypeMustBeZero = (value... | 2021-04-16T05:36:39 | 2021-04-16T05:44:31 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.