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 | 1,017,989,004 | 5,297 | smolgumball | That makes sense, but I'd think that internal `warn`'s shouldn't be issued outside the scope of a component if that's the case. Having a `warnHandler` override that doesn't override all uses of `warn` seems unintuitive.
Would it be possible for `warnHandler` to be invoked with alternative arguments in the case that ... | 2022-01-20T22:38:41 | 2022-01-20T22:38:41 | {
"+1": 1
} | NONE |
vuejs | core | 1,018,686,019 | 4,619 | aantipov | Hey 👋 any news here? | 2022-01-21T16:54:49 | 2022-01-21T16:54:49 | {} | NONE |
vuejs | core | 1,014,561,519 | 5,277 | edison1105 | duplicate of #4930 | 2022-01-17T13:41:34 | 2022-01-17T13:41:34 | {} | MEMBER |
vuejs | core | 1,017,161,536 | 5,293 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 0c9cc894e8545923108f41c24b2f1c6d82f4e029
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/61e901cd79ea080007108ba8](https://app.netlify.com/sites/vue-sfc-playground/deploys/61e901cd79ea080007108ba8)
... | 2022-01-20T06:31:46 | 2022-01-20T06:34:21 | {} | NONE |
vuejs | core | 1,018,117,103 | 5,289 | edison1105 | caused by:
- force block for custom dirs
- `svg` and `foreignObject` also force block
- `svg` + custom dirs also force block, but here we skip the logic
https://github.com/vuejs/core/blob/4768f26f591551b222aa9a2cc73791f8bff9f5f7/packages/compiler-core/src/transforms/hoistStatic.ts#L171-L177 | 2022-01-21T02:49:23 | 2022-01-21T02:58:44 | {
"+1": 3
} | MEMBER |
vuejs | core | 1,018,224,337 | 5,236 | cool-little-fish | sorry to comment under a closed issue, but If I want to continue to use the migration build, is there a possible workaround for this case ?@yyx990803 | 2022-01-21T06:39:06 | 2022-01-21T06:39:06 | {} | CONTRIBUTOR |
vuejs | core | 1,016,546,431 | 5,291 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 06aba4a53c338be4a83678e5692024a1d8e17091
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/61ea56743d9f2c00077ca3a0](https://app.netlify.com/sites/vuejs-coverage/deploys/61ea56743d9f2c00077ca3a0)
😎 Browse th... | 2022-01-19T14:56:28 | 2022-01-21T06:50:31 | {} | NONE |
vuejs | core | 1,014,588,065 | 5,273 | posva | Also, please open issues in English only in this repo, thanks. | 2022-01-17T14:13:04 | 2022-01-17T14:13:04 | {} | MEMBER |
vuejs | core | 1,017,161,535 | 5,293 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 0c9cc894e8545923108f41c24b2f1c6d82f4e029
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/61e901cd256da20008c16f4f](https://app.netlify.com/sites/vue-next-template-explorer/deploys/61e... | 2022-01-20T06:31:46 | 2022-01-20T06:32:42 | {} | NONE |
vuejs | core | 1,017,251,162 | 5,272 | yyx990803 | I guess what you want is a separate `ExtractExternalPropTypes`? | 2022-01-20T08:58:13 | 2022-01-20T08:58:13 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,019,315,081 | 5,308 | lidlanca | introduced by: https://github.com/vuejs/core/commit/ed9eb62e5992bd575d999c4197330d8bad622cfb | 2022-01-22T17:32:39 | 2022-01-22T17:32:39 | {} | CONTRIBUTOR |
vuejs | core | 1,019,463,361 | 5,310 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 9fe8b45a6ac64c61c377486aba7c8afad5b0f711
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/61ed3a033612ef0007f5e8c7](https://app.netlify.com/sites/vuejs-coverage/deploys/61ed3a033612ef0007f5e8c7)
😎 Browse th... | 2022-01-23T11:20:39 | 2022-01-23T11:25:55 | {} | NONE |
vuejs | core | 1,014,842,319 | 5,271 | lidlanca | when initialized `reactive({...})` state, preserved the shallow proxy
```js
const getData = () => shallowReactive([{ id: 1 }])
const state = reactive({ data: getData() })
```
however the `data` property is part of a reactive object, and when you set that property
with a new `shallowReactive` object, vue r... | 2022-01-17T19:43:58 | 2022-01-17T19:48:58 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,015,369,356 | 5,247 | edison1105 | same as #5102 #5273
> Once a <suspense> has resolved the contents of its default slot, it can only be triggered again if the default root node is replaced. New components nested deeper in the tree are not sufficient to move the back into a pending state. | 2022-01-18T12:35:46 | 2022-01-18T12:38:06 | {} | MEMBER |
vuejs | core | 1,015,373,836 | 5,247 | LinusBorg | Not really. In this issue here, there *is* only one component root node in the default slot, and it *is* being replaced. It's just that the default slot containing that single root node is being passed through from a parent to Suspense.
The problem as it seems to me is that the compiler has wrapped it in a Fragme... | 2022-01-18T12:42:06 | 2022-01-18T12:43:07 | {} | MEMBER |
vuejs | core | 1,018,217,095 | 5,243 | yyx990803 | `unref()` simply unwraps the refs, not reactivity. The current behavior is intended behavior and this change will be a breaking change. | 2022-01-21T06:22:49 | 2022-01-21T06:22:49 | {} | MEMBER |
vuejs | core | 1,018,235,502 | 5,251 | yyx990803 | Added logic for recursive mixins with mixins. | 2022-01-21T07:01:56 | 2022-01-21T07:01:56 | {} | MEMBER |
vuejs | core | 1,019,073,769 | 5,306 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 998cf37e1b0e7d83c9302bfdd26e231ced5da293
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/61ed19689307b30007777134](https://app.netlify.com/sites/vue-sfc-playground/deploys/61ed19689307b30007777134)
... | 2022-01-22T06:21:20 | 2022-01-23T09:03:48 | {} | NONE |
vuejs | core | 1,019,463,363 | 5,310 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 9fe8b45a6ac64c61c377486aba7c8afad5b0f711
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/61ed3a03c6928000070b1ee0](https://app.netlify.com/sites/vue-sfc-playground/deploys/61ed3a03c6928000070b1ee0)
... | 2022-01-23T11:20:39 | 2022-01-23T11:23:03 | {} | NONE |
vuejs | core | 1,014,096,932 | 5,213 | timongh | > Force trigger the ref with `triggerRef()`: https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgdHJpZ2dlclJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgdGV4dCA9IHJlZignMycpXG5cbmZ1bmN0aW9uIG9uSW5wdXQoZXZlbnQpIHtcbiAgdGV4dC52YWx1ZSA9IGV2ZW50LmRhdGFcbiAgdHJpZ2dlclJlZih0ZXh0KVxufVxuPC9zY3JpcHQ+XG5cbjx0ZW1w... | 2022-01-17T03:10:04 | 2022-01-17T03:10:04 | {} | NONE |
vuejs | core | 1,014,506,929 | 5,252 | edison1105 | The `<router-view/>` of the child route, also has to be wrapped by `keepalive`. | 2022-01-17T13:03:27 | 2022-01-17T13:03:27 | {} | MEMBER |
vuejs | core | 1,014,513,898 | 5,275 | edison1105 | Please provide a working demo | 2022-01-17T13:08:35 | 2022-01-17T13:08:35 | {} | MEMBER |
vuejs | core | 1,014,958,545 | 5,272 | yyx990803 | `ExtractPropsTypes`'s return type is the type of the internal normalized props (i.e. what the child component sees), not the expected external props (i.e. what the parent component is passing). | 2022-01-17T23:47:19 | 2022-01-17T23:47:55 | {} | MEMBER |
vuejs | core | 1,015,502,774 | 5,282 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 9b265ee9ccf12afd5e47dcf5eeb501e5720bc700
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/61e6d7615deb1800087d7fcf](https://app.netlify.com/sites/vue-next-template-explorer/deploys/61e... | 2022-01-18T15:06:15 | 2022-01-18T15:07:04 | {} | NONE |
vuejs | core | 1,017,211,190 | 5,295 | edison1105 | 只看截图是看无法看出实际问题的。请提供一个**简单可运行的** demo。 | 2022-01-20T08:03:42 | 2022-01-20T08:03:42 | {} | MEMBER |
vuejs | core | 1,017,955,836 | 5,290 | lidlanca | > maybe we could code like this,put the action to nexttick
no need
```js
export default {
beforeCreate() {
this.obj = {}
},
mounted() {
this.obj.a = 1;
},
unmounted() {
delete this.obj;
}
}
```
| 2022-01-20T21:46:51 | 2022-01-20T21:46:51 | {} | CONTRIBUTOR |
vuejs | core | 1,018,231,310 | 5,291 | yyx990803 | There is already a block handling similar problem for `:key` so they should be moved together. | 2022-01-21T06:54:33 | 2022-01-21T06:54:33 | {} | MEMBER |
vuejs | core | 1,018,258,770 | 5,239 | jaulz | @yyx990803 thanks for your feedback and explains a lot! 😊 Maybe it's worth a renaming (e.g. with a prefix) to indicate internal usage only? | 2022-01-21T07:42:53 | 2022-01-21T07:42:53 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 995,386,255 | 5,109 | Justineo | @lidlanca Your comment is inappropriate. Please follow our [code of conduct](https://github.com/vuejs/vue/blob/dev/.github/CODE_OF_CONDUCT.md) which helps maintaining a healthy community. | 2021-12-16T02:37:57 | 2022-01-21T07:47:06 | {
"-1": 1
} | MEMBER |
vuejs | core | 1,019,463,362 | 5,310 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 9fe8b45a6ac64c61c377486aba7c8afad5b0f711
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/61ed3a038b88680008179654](https://app.netlify.com/sites/vue-next-template-explorer/deploys/61e... | 2022-01-23T11:20:39 | 2022-01-23T11:21:28 | {} | NONE |
vuejs | core | 1,015,411,867 | 5,247 | edison1105 | @LinusBorg
You are right.
I'm trying to say : maybe, it would be better to let `Suspense` back into the pending status when the default slot re-render. | 2022-01-18T13:27:33 | 2022-01-18T13:27:33 | {} | MEMBER |
vuejs | core | 1,015,951,219 | 5,284 | lidlanca | This seem to be the a documented feature for vue 3, which is not vue 2 .
as a workaround for this use case, you can use .trim modifier to get a string
```js
<input type="number" v-model.trim="phon... | 2022-01-19T00:15:19 | 2022-01-19T00:15:19 | {} | CONTRIBUTOR |
vuejs | core | 1,016,370,025 | 5,284 | lidlanca | perhaps vue should not have casted by default, keep this issue open, see what core team has to say.
feel free to suggest improvement to the docs if you find the current phrasing confusing
https://github.com/vuejs/docs/issues
also note that the docs will soon be updated to this, which I find even more misleadin... | 2022-01-19T11:30:51 | 2022-01-19T11:31:20 | {} | CONTRIBUTOR |
vuejs | core | 1,016,387,369 | 5,284 | jacekkarczmarczyk | This was working properly in earlier 3.x versions but then the breaking change was introduced (https://github.com/vuejs/core/issues/3813, https://github.com/vuejs/core/blob/main/CHANGELOG.md#320-beta2-2021-07-19) | 2022-01-19T11:45:26 | 2022-01-19T12:26:32 | {} | CONTRIBUTOR |
vuejs | core | 1,016,880,431 | 4,662 | Makoehle | I've found a [blog](https://maximomussini.com/posts/vue-custom-elements/) by @ElMassimo describing a workaround which works for me. To summarize:
1. Name all SFC file names `*.ce.vue`
2. In your `main.ts` use [defineCustomElement](https://v3.vuejs.org/guide/web-components.html#definecustomelement).
3. [Define](ht... | 2022-01-19T21:23:19 | 2022-01-19T21:23:19 | {
"+1": 5,
"hooray": 2
} | NONE |
vuejs | core | 1,018,138,433 | 5,250 | weiquanju | When can you fix this bug? | 2022-01-21T03:38:27 | 2022-01-21T03:38:27 | {} | NONE |
vuejs | core | 1,018,222,033 | 5,236 | yyx990803 | Vue 3's resolving logic self-resolves if the component's name option matches. That's the intended behavior. ViewUI should add a prefix to the `name` option to all components that have overlapping name with native HTML elements.
Prefix-less components + native element name is explicitly prohibited in the style guide. | 2022-01-21T06:33:20 | 2022-01-21T06:34:06 | {} | MEMBER |
vuejs | core | 1,018,228,627 | 5,251 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 2f3510abef96079270a4870f5ab4948ecddb91ae
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/61ea58cbfbf60300083a76e0](https://app.netlify.com/sites/vuejs-coverage/deploys/61ea58cbfbf60300083a76e0)
😎 Browse th... | 2022-01-21T06:48:34 | 2022-01-21T07:01:35 | {} | NONE |
vuejs | core | 1,005,974,257 | 3,348 | 07akioni | I think a helper function that modifies dynamicProps would be fine = =... | 2022-01-05T18:28:00 | 2022-01-05T18:28:00 | {} | CONTRIBUTOR |
vuejs | core | 1,007,488,240 | 5,220 | LinusBorg | For your specific use case, you can just switch from declaring an event to a prop:
```js
props: ['onClose'],
// instead of:
emits: ['close'],
```
Event Listeners are passed as props with an `on` prefix, so these two declarations both represent an event. Meaning, if you have an `onClose` prop, calling `emit('c... | 2022-01-07T15:17:21 | 2022-01-07T15:17:56 | {
"heart": 4
} | MEMBER |
vuejs | core | 1,008,224,219 | 5,226 | Wawa27 | Yes, I've also tried adding differents keys to both vnodes but only the second vnode is visible, but I'd like them to be both visible.
I'm expecting something like this :
| 2022-01-09T03:53:43 | 2022-01-09T03:53:43 | {} | NONE |
vuejs | core | 1,008,234,841 | 5,215 | zhangenming | > Well, I would say maybe some third-party libraries need these interal api.
I didn't catch what you said, Can you give me an example? Thank you
Maybe `types declaration` can have this problem? | 2022-01-09T05:43:23 | 2022-01-09T05:43:23 | {} | CONTRIBUTOR |
vuejs | core | 1,008,950,092 | 5,234 | LinusBorg | I'd not rate this a bug as the SFC spec explicitly states that the style scoping only extends to the root element of a child component, but I see a use in discussing how to enhance the behaviour for this specific usecase
In the meantime, we have `:deep()` to extend styles to deeply nested elements as well as css mod... | 2022-01-10T14:54:27 | 2022-01-10T14:54:27 | {} | MEMBER |
vuejs | core | 1,003,386,772 | 5,148 | edison1105 | @posva
if change the `<style scoped>` to ` <style>` , it works fine. see https://codesandbox.io/s/white-river-3mf6q
here is no `scopedId`
| 2021-12-31T14:15:08 | 2021-12-31T14:19:57 | {} | MEMBER |
vuejs | core | 1,004,096,066 | 1,033 | fobdy | For me latest `@vue/runtime-dom` is also conflicting internally.
excluding `**/*.stories.ts` and including `vite/client` doesn't prevent `@vue/runtime-dom` having conflict with `@types/react`. I have no idea where VS Code's TS might grab the React types, but we have `@storybook/vue` installed and some `*.ts` storybook... | 2022-01-03T13:33:53 | 2022-01-03T13:33:53 | {} | NONE |
vuejs | core | 1,004,698,423 | 5,205 | LinusBorg | I don't see this why this should be seen as a bug. You should not be relying on
1) internal APIs like `instance.deactivated`
2) assumptions about timing in Vue's asynchronous update process that are not documented.
You should rather be using `onActivated`/`onDeactivated` to react to when an instance is *actuall... | 2022-01-04T10:38:02 | 2022-01-04T10:38:02 | {} | MEMBER |
vuejs | core | 1,005,890,308 | 5,213 | timongh | A similar problem exists in vue 2, but I haven't tested the version specifically. | 2022-01-05T16:43:53 | 2022-01-05T16:43:53 | {} | NONE |
vuejs | core | 1,006,415,482 | 2,513 | semiaddict | I am also encountering this issue when mounting a component into an empty iframe.
The first click events are ignored. It can last a few seconds before click events are finally emitted.
Since the time check fix concerns only rare edge cases and introduces bugs in other cases, it might be interesting to allow disabli... | 2022-01-06T09:38:19 | 2022-01-06T09:38:19 | {} | NONE |
vuejs | core | 1,007,921,718 | 5,225 | LinusBorg | See my reply in #5224 | 2022-01-08T09:22:52 | 2022-01-08T09:22:52 | {} | MEMBER |
vuejs | core | 1,008,221,061 | 5,215 | caozhong1996 | Well, I would say maybe some third-party libraries need these interal api. | 2022-01-09T03:19:19 | 2022-01-09T03:19:19 | {} | CONTRIBUTOR |
vuejs | core | 1,008,314,967 | 5,220 | LinusBorg | @squal The fact that you need to reach into the internal component instance makes this a bit brittle. I'd rate this a workaround more than a proper solution and would still be in favor to have something more stable in core. | 2022-01-09T15:07:30 | 2022-01-09T15:07:30 | {
"+1": 1,
"eyes": 1
} | MEMBER |
vuejs | core | 1,008,472,825 | 4,294 | mareszhar | > 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.
Thank you so much for making this, @wheatjs ❤️ ! In the future, I'd also like to help fix this kind of issues. Do you have any pointers on what one should learn to b... | 2022-01-10T01:18:54 | 2022-01-10T01:18:54 | {} | NONE |
vuejs | core | 1,004,773,186 | 5,202 | LinusBorg | Caused by these lines:
https://github.com/vuejs/vue-next/blob/eb721d49c004abf5eff0a4e7da71bad904aa6bac/packages/runtime-dom/src/directives/vModel.ts#L138-L143
I *think* that code should work as well if it was in a `beforeMount`, need to try later. if so, should solve the bug.
Edit: Similar issue likely here:
... | 2022-01-04T12:37:09 | 2022-01-04T12:43:24 | {} | MEMBER |
vuejs | core | 1,005,167,214 | 1,228 | mgdodge | Any word on a fix for this? Using vite 2.7.10, vue 3.2.6, and this still comes up if I don't manually override. Offending lines in the generated typescript defs are now 1215-1216, 1405, 1758 and 1787. Those are the following:
```ts
// 1215-1216: The "declare type" line itself is fine, the issue is just the referenc... | 2022-01-04T21:01:18 | 2022-01-04T21:01:18 | {} | NONE |
vuejs | core | 1,006,340,418 | 5,204 | caozhong1996 | Your code isn't working properly, maybe you should do like this:
| 2022-01-06T07:23:48 | 2022-01-06T07:23:48 | {} | CONTRIBUTOR |
vuejs | core | 1,008,361,854 | 5,227 | aantipov | @lidlanca thank you 👍 Good to know about it. I'll definitely consider that rfc if I decide to open another one | 2022-01-09T19:46:08 | 2022-01-09T19:46:08 | {} | NONE |
vuejs | core | 1,003,114,323 | 5,189 | LinusBorg | Not sure I would want to rate this a bug. the `<template v-if></template>` wrapper results in a Fragment root node, because it could potentially contain multiple child elements - and Fragments don't inherit attributes. Technically, that feels correct. Yet it works dev, so somthing *is* off.
Either way, this is a low... | 2021-12-30T17:14:11 | 2021-12-30T17:16:17 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,003,243,538 | 5,167 | cloudcome | @posva
The background is: I have a global style class name `global` on the html tag, and my component has a local style class name `scoped`.
# the source code
```vue
<template>
<h1 class="scoped">1</h1>
</template>
<style scoped>
:deep(.global) .scoped {
color: #f00;
}
.scoped :deep(... | 2021-12-31T02:24:34 | 2021-12-31T02:28:03 | {} | NONE |
vuejs | core | 1,007,770,056 | 5,222 | oswaldofreitas | here you go: https://github.com/oswaldofreitas/vue-compat-issue | 2022-01-07T21:59:37 | 2022-01-07T21:59:37 | {
"+1": 5
} | NONE |
vuejs | core | 1,008,220,167 | 5,226 | caozhong1996 | Maybe you need a key ?
| 2022-01-09T03:11:43 | 2022-01-09T03:11:43 | {} | CONTRIBUTOR |
vuejs | core | 1,008,295,725 | 5,227 | LinusBorg | This is working as intended. `toRaw()`'s use case is to give you the *original* object that a `reactive()` proxy is wrapping. If that original plain object contains refs, they were part of the original and therefore will be in the result of `toRaw(). It's a very cheap operation as it only needs to do one lookup of the ... | 2022-01-09T13:12:32 | 2022-01-09T13:18:11 | {} | MEMBER |
vuejs | core | 1,008,322,792 | 5,227 | aantipov | Thanks a lot for thorough explanation!
I understand this now. Agree that it's better not to touch `toRaw()`'s current behaviour.
Thanks for the RFC suggestion. I might open a discussion there
| 2022-01-09T15:49:51 | 2022-01-09T15:49:51 | {} | NONE |
vuejs | core | 1,004,461,104 | 4,654 | adamreisnz | I find that when making changes to components that have a `v-if` or `v-show` condition on them (for example a dropdown menu), and I make some changes to a nested component, this will hot-reload fine when the component is visible. But if I then toggle the visibility of the parent component to hide it and then show it ag... | 2022-01-04T01:15:38 | 2022-01-04T01:15:38 | {} | NONE |
vuejs | core | 1,004,463,521 | 5,201 | edison1105 | @bart
as @lidlanca said. use `v-memo` for this scenario. | 2022-01-04T01:23:03 | 2022-01-04T01:23:03 | {} | MEMBER |
vuejs | core | 1,004,804,215 | 5,196 | maritaria | Looking at the [MDN docs for the Function constructor](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function#difference_between_function_constructor_and_function_declaration) shows that code compiled this way can only ever reference global variables.
This means that in order to reso... | 2022-01-04T13:19:25 | 2022-01-04T13:19:25 | {} | NONE |
vuejs | core | 1,005,750,646 | 5,210 | LinusBorg | I think in a way, it's correct. what you wrote is a shorter variant of:
```html
<Comp>
<template #default>
<h1 v-if="true">H1</h1>
</template>
<template v-else #my-slot>
This should render
</template>
</Comp>
```
As you can see, the `v-if` and `v-else` are not *actually* on the same level... | 2022-01-05T14:49:26 | 2022-01-05T14:49:51 | {} | MEMBER |
vuejs | core | 1,005,800,706 | 4,294 | nborko | I've gone all-in on Vue 3, TypeScript and the Composition API. However, the restriction of requiring object literals and interfaces being defined in the SFC source severely limits reuse.
I am attempting to define a common props interface in a composable module to replace the need for a mixin, extending Props interfa... | 2022-01-05T15:25:43 | 2022-01-05T15:25:43 | {
"+1": 24
} | NONE |
vuejs | core | 1,006,448,111 | 5,194 | ghost | @edison1105 @HcySunYang Please review 😅. | 2022-01-06T10:21:49 | 2022-01-06T10:21:49 | {} | NONE |
vuejs | core | 1,007,508,075 | 5,219 | itkui | > 直接使用onVnodeMounted作为prop名字会命中这个特殊逻辑从而导致错误
是的，这里逻辑错误确实是因为这里作为prop名字（测试的时候忘记了:冒号），命中了这个特殊逻辑。
不过我传递onVnodeMounted确实得到的结果和@vnode-mounted是一致的。
```vue
<template>
<!-- 这两者结果一致 -->
<custom-component :onVnodeMounted="onVnodeMounted"></custom-component>
<custom-component @vnode-mounted="onVnodeMounted"><... | 2022-01-07T15:42:36 | 2022-01-07T15:49:51 | {} | NONE |
vuejs | core | 1,008,274,789 | 5,226 | LinusBorg | https://v3.vuejs.org/api/application-api.html#mount
> The innerHTML of the provided DOM element will be replaced with the rendered template of the application root component.
The same happens when you directly use `render()` (which `app.mount()` wraps). | 2022-01-09T10:57:11 | 2022-01-09T10:57:11 | {} | MEMBER |
vuejs | core | 1,003,537,652 | 5,196 | edison1105 | ```javascript
(function() {
'use strict';
window.Vue = Vue // add this line
Vue.createApp({
data() {
return {
foo: 'bar'
}
},
template: '{{ foo }}'
}).mount('#app');
})();
``` | 2022-01-01T10:20:10 | 2022-01-01T10:20:10 | {} | MEMBER |
vuejs | core | 1,004,169,262 | 5,199 | 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... | 2022-01-03T15:28:27 | 2022-01-03T15:28:27 | {} | CONTRIBUTOR |
vuejs | core | 1,005,919,480 | 5,213 | sqal | I believe that this is the same case as https://github.com/vuejs/vue/issues/7506#issuecomment-372139382 and it always worked like that
When you type `"a"`, component re-renders because previous value of `text` was `"3"`, but when you type the same letter for the second time, component won't update because value has ... | 2022-01-05T17:18:30 | 2022-01-05T17:18:30 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,007,201,029 | 5,217 | qq10137383 | @edison1105
确实和 #4984 差不多的问题，用你的方法解决了，感谢！
```
<script lang="ts">
import { defineComponent，computed } from 'vue'
import { useStore } from 'vuex'
export default defineComponent({
name: 'AppMain',
setup() {
const store = useStore();
const cachedViews = computed(() => [...store.getter... | 2022-01-07T07:37:40 | 2022-01-07T07:43:32 | {} | NONE |
vuejs | core | 1,007,290,642 | 5,213 | shadowings-zy | I think the reason of this bug is the `hasChanged` function in here: https://github.com/vuejs/vue-next/blob/master/packages/reactivity/src/baseHandlers.ts#L170
In this case, the text you input is same as you input before, so it will not trigger effect or update component.
If we remove the `hasChanged` function, t... | 2022-01-07T10:14:18 | 2022-01-07T10:14:18 | {} | CONTRIBUTOR |
vuejs | core | 1,007,761,172 | 5,222 | LinusBorg | Can your provide this as a repository? I can neither edit nor download that code without registering for this service which I don't use. | 2022-01-07T21:43:32 | 2022-01-07T21:43:32 | {} | MEMBER |
vuejs | core | 1,008,221,683 | 4,070 | guxuerui | I'm using the latest version of vue@3.2.26, but I still have this problem.
| 2022-01-09T03:25:34 | 2022-01-09T03:25:34 | {} | NONE |
vuejs | core | 1,008,316,137 | 4,294 | webpig | wait | 2022-01-09T15:14:05 | 2022-01-09T15:47:07 | {} | NONE |
vuejs | core | 1,008,351,856 | 5,230 | 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... | 2022-01-09T18:40:07 | 2022-01-09T18:40:07 | {} | CONTRIBUTOR |
vuejs | core | 1,003,300,932 | 5,167 | posva | The generated CSS is correct, see https://v3.vuejs.org/api/sfc-style.html#style-scoped. You probably just need `.global .scoped` with nothing as I said before.
Please, use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) for further questions. | 2021-12-31T07:58:36 | 2021-12-31T07:58:36 | {} | MEMBER |
vuejs | core | 1,004,383,955 | 5,201 | lidlanca | maybe `v-memo`
```js
<Row v-for="row in tableData" :key="row.id" class="flex" :row="row" v-memo="[row.id]" >
``` | 2022-01-03T21:53:56 | 2022-01-03T21:53:56 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,005,491,507 | 4,949 | Edge00 | > You need to run https://github.com/vuejs/vue-next/blob/master/package.json#L25 first
I use node 16.5.0 pnpm 6.24.4 and i have same problen @posva | 2022-01-05T08:49:54 | 2022-01-05T08:50:04 | {} | NONE |
vuejs | core | 1,007,202,302 | 5,218 | edison1105 | This might be a good feature.
same as https://github.com/vuejs/vue-next/pull/4997#issuecomment-994925085 | 2022-01-07T07:40:56 | 2022-01-07T07:41:03 | {} | MEMBER |
vuejs | core | 1,008,319,240 | 4,294 | LinusBorg | @nborko Would it be possible for you to work with actual props objects instead of TS interfaces? Or does that raise other issues in your workflow? i.e. this works fine:
```js
// Props.ts
export const defaultProps = {
age: {
type: Number,
required: true,
},
job: {
type: String,
default:... | 2022-01-09T15:30:49 | 2022-01-09T15:40:37 | {
"eyes": 3
} | MEMBER |
vuejs | core | 1,008,689,206 | 5,221 | wirk | Thanks for the reply. I actually checked the changelog before and failed to see that entry 🙈. I feel like this might have warranted a new minor version instead of a patch version because it breaks existing code that uses unique ref names in v-for ✌️ | 2022-01-10T09:33:48 | 2022-01-10T09:33:48 | {} | NONE |
vuejs | core | 1,003,238,725 | 5,191 | zouhangwithsweet | Composition API YES！
I have refactor all components in [mand-mobile-next](https://github.com/mand-mobile/mand-mobile-next) with VCA. It's pretty cool for code organization. I think we should write less in .vue
write more in useXx.ts
And I will use Setup sugar to minimize the codes in .vue | 2021-12-31T01:58:04 | 2021-12-31T01:58:04 | {} | CONTRIBUTOR |
vuejs | core | 1,003,538,731 | 5,196 | edison1105 | @YanxinTang OK, keep this opened. | 2022-01-01T10:32:04 | 2022-01-01T10:32:04 | {} | MEMBER |
vuejs | core | 1,005,761,356 | 5,210 | oswaldofreitas | oh I see, you're right! Thank you | 2022-01-05T15:01:11 | 2022-01-05T15:01:11 | {} | NONE |
vuejs | core | 1,007,757,461 | 5,223 | LinusBorg | This is a missing piece in the docs, but not an issue for this repository. We will make sure to cover it in the upcoming new docs. | 2022-01-07T21:35:54 | 2022-01-07T21:35:54 | {} | MEMBER |
vuejs | core | 1,008,239,757 | 5,226 | caozhong1996 | Well, then you should merge two Vnodes and it's not a bug. | 2022-01-09T06:35:02 | 2022-01-09T06:35:02 | {} | CONTRIBUTOR |
vuejs | core | 1,008,948,024 | 5,219 | daixiongsheng | > > 直接使用onVnodeMounted作为prop名字会命中这个特殊逻辑从而导致错误
>
> 是的，这里逻辑错误确实是因为这里作为prop名字（测试的时候忘记了:冒号），命中了这个特殊逻辑。 不过我传递onVnodeMounted确实得到的结果和@vnode-mounted是一致的。
>
> ```
> <template>
> <!-- 这两者结果一致 -->
> <custom-component :onVnodeMounted="onVnodeMounted"></custom-component>
> <custom-component @vnode-mounted="o... | 2022-01-10T14:52:20 | 2022-01-10T14:52:54 | {
"+1": 2
} | NONE |
vuejs | core | 1,003,303,511 | 5,191 | posva | Closing as this is not the right place to ask questions and more than enough feedback has been provided.
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-12-31T08:09:33 | 2021-12-31T08:09:33 | {} | MEMBER |
vuejs | core | 1,003,538,384 | 5,196 | YanxinTang | Tampermonkey user script is running in the sandbox to avoid pollution the global scope.
Apparently registry the Vue in global scope will break the peace.
This solution can work but can't work perfectly. | 2022-01-01T10:28:20 | 2022-01-01T10:28:20 | {} | NONE |
vuejs | core | 1,004,330,185 | 5,203 | vincerubinetti | More info:
**Error message**
```
Extraneous non-props attributes (class) were passed to component but could not be automatically inherited because component renders fragment or text root nodes.
at <HelloWorld class="red">
```
**App**
```vue
<template>
<HelloWorld class="red">Test</HelloWorld>
</tem... | 2022-01-03T20:12:01 | 2022-01-03T20:12:01 | {} | NONE |
vuejs | core | 1,005,320,565 | 5,196 | YanxinTang | Yes, I have created a pull request for this problem. [https://github.com/vuejs/vue-next/pull/5197](https://github.com/vuejs/vue-next/pull/5197) | 2022-01-05T02:09:02 | 2022-01-05T02:09:02 | {} | NONE |
vuejs | core | 1,005,345,248 | 5,206 | edison1105 | see #5193 | 2022-01-05T03:11:50 | 2022-01-05T03:11:50 | {} | MEMBER |
vuejs | core | 1,006,346,477 | 5,212 | caozhong1996 | Just a reminder, they are correlated😃 #5048 | 2022-01-06T07:37:33 | 2022-01-06T07:37:33 | {} | CONTRIBUTOR |
vuejs | core | 1,007,894,356 | 4,294 | mesqueeb | Is there any way we can donate for specific issues? Or maybe open an issue hunt? I'd love to put in some extra donations specifically towards this ticket. | 2022-01-08T06:13:05 | 2022-01-08T06:13:05 | {
"+1": 44
} | NONE |
vuejs | core | 1,008,622,885 | 4,997 | honghuangdc | > Can Official support the Syntactic sugar？ https://github.com/anncwb/vite-plugin-vue-setup-extend
>
> ```
> <template>
> <div>hello world {{ a }}</div>
> </template>
>
> <script lang="ts" setup name="App">
> const a = 1
> </script>
> ```
if the component name is a variable, can this syntactic sugar ... | 2022-01-10T08:07:43 | 2022-01-10T08:07:43 | {} | NONE |
vuejs | core | 1,005,719,560 | 5,208 | levchak0910 | Updated reproduction description | 2022-01-05T14:13:06 | 2022-01-05T14:13:06 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.