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,022,368,545 | 4,566 | LinusBorg | But it already says it has to be set "in the child component".
And on top, the migration guide explains that all Compat flags that need to be set in the compiler Options are prefixed with COMPILER_*
I'm not sure how to make it more clear, do you have a concrete suggestion? | 2022-01-26T16:27:53 | 2022-01-26T16:28:39 | {} | MEMBER |
vuejs | core | 1,023,075,463 | 5,322 | posva | This seems to be just how CSS variables work:
```js
$0.style.setProperty('--color', undefined) // sets the string undefined
``` | 2022-01-27T10:42:41 | 2022-01-27T10:42:41 | {} | MEMBER |
vuejs | core | 1,024,727,755 | 5,333 | lidlanca | one can also disable attributes inheritance
```js
inheritAttrs:false
```
and manually pass attributes to the next child
```html
// age is passthrough
// name is override
<CompChild name="Set by comp" v-bind:age=$attrs.age></CompChild>
```
[SFC Playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBz... | 2022-01-28T23:01:46 | 2022-01-28T23:01:54 | {} | CONTRIBUTOR |
vuejs | core | 1,019,732,498 | 4,314 | flozero | Same here it is a huge need in our company or we will miss the train for vue3 and just go for lit | 2022-01-24T05:21:49 | 2022-01-24T05:22:00 | {
"+1": 10
} | NONE |
vuejs | core | 1,020,184,245 | 5,314 | flozero | Definitely working thank you ! What would be the best practice with a vue2 project . Ref to https://github.com/vuejs/core/issues/5313 | 2022-01-24T14:54:28 | 2022-01-24T14:54:28 | {} | NONE |
vuejs | core | 1,020,200,756 | 5,314 | LinusBorg | Please take further questions back to discord. | 2022-01-24T15:09:54 | 2022-01-24T15:09:54 | {} | MEMBER |
vuejs | core | 1,021,364,833 | 5,325 | LinusBorg | You could use one prop and have it accept ob object like `{ height: number, width: number }`
Or validate the combo in a computed property. | 2022-01-25T16:22:40 | 2022-01-25T16:23:10 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,022,813,425 | 4,339 | dfengwei | Looking forward to this feature | 2022-01-27T03:27:35 | 2022-01-27T03:27:35 | {} | NONE |
vuejs | core | 1,023,598,289 | 5,331 | ktfth | What is the definition for the feature who is good to discuss? | 2022-01-27T20:10:50 | 2022-01-27T20:10:50 | {} | NONE |
vuejs | core | 1,021,513,191 | 5,328 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 6dff8a25a61243e0c26c258ddedfa65debb0228e
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f04cc97c5dc700079c1481](https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f... | 2022-01-25T19:03:40 | 2022-01-25T19:18:26 | {} | NONE |
vuejs | core | 1,022,993,250 | 5,333 | LinusBorg | I'll reopen this to re-evaluate one specific thing: attrs from parent overrwriting explicit props in the child, like this: [Playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCBDb21wIGZyb20gJy4vQ29tcC52dWUnXG4gIGltcG9ydCBDb21wQSBmcm9tICcuL0NvbXBBLnZ1ZSdcbjwvc2NyaXB0PlxuXG48dGVtcGxhdGU+XG4gI... | 2022-01-27T09:07:23 | 2022-01-27T09:07:53 | {} | MEMBER |
vuejs | core | 1,023,317,286 | 5,031 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 35f59b3c2274711cdc0372a4e6258a37b4cd875e
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f2b6e220abbe0009195dd9](https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f... | 2022-01-27T15:14:47 | 2022-01-27T15:15:32 | {} | NONE |
vuejs | core | 1,023,990,775 | 5,337 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: e87c843bf53f8aeeddec1b9f2a28ebe68f63cdea
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/61f3a9063c2e7700071546cc](https://app.netlify.com/sites/vuejs-coverage/deploys/61f3a9063c2e7700071546cc)
😎 Browse th... | 2022-01-28T08:27:56 | 2022-01-28T08:34:10 | {} | NONE |
vuejs | core | 1,019,487,145 | 5,301 | LinusBorg | Can you maybe share a more detailed list of "those TS errors" and your ev.d.ts file which you may have altered? | 2022-01-23T13:36:16 | 2022-01-23T13:36:16 | {} | MEMBER |
vuejs | core | 1,019,920,987 | 1,327 | Norserium | @yyx990803, it's been almost two years, but there are no stable alternatives of `vue-server-renderer` for Vue 3.
There are two biggest players on the server side rendering field: Quasar and Nuxt. Both of them have to use forks of `vue-server-renderer` under the hood or re-implement its parts.
Quasar:
- [Server P... | 2022-01-24T10:02:31 | 2022-01-24T12:11:17 | {
"+1": 7
} | NONE |
vuejs | core | 1,020,195,880 | 5,314 | flozero | Also the event are not working in the react project. Is it a limitation from react ? | 2022-01-24T15:05:30 | 2022-01-24T15:05:30 | {} | NONE |
vuejs | core | 1,021,360,843 | 5,324 | LinusBorg | Vue events can have more than one argument,
```js
this.$emit('event', 1, 2, 3)
```
but CustomEvent only has one payload: event.detail
```js
new CustomEvent({
detail: [1, 2, 3]
})
```
So we have to use an array in case a component wants to emit more than one thing.
it's also documented in the new... | 2022-01-25T16:19:57 | 2022-01-25T16:21:02 | {} | MEMBER |
vuejs | core | 1,021,407,571 | 5,324 | LinusBorg | You mean like this? 🤔
https://v3.vuejs.org/api/instance-methods.html#emit
Vue 2 docs have basically the same sentence as well. | 2022-01-25T17:01:14 | 2022-01-25T17:02:40 | {} | MEMBER |
vuejs | core | 1,021,413,872 | 5,324 | adamdehaven | 😂 yep, exactly like that. | 2022-01-25T17:07:41 | 2022-01-25T17:07:41 | {
"laugh": 1
} | NONE |
vuejs | core | 1,021,433,946 | 5,327 | LinusBorg | This isn't really a bug. Here's what's happening:
* Vue 3 reactivity relies on a few singletons in that reactivity package.
* You built your library and excluded 'vue', as you should, but since you imported from '@vue/reactivity', that package got bundled with your library.
* So now the consuming app has two copie... | 2022-01-25T17:28:20 | 2022-01-25T17:29:27 | {} | MEMBER |
vuejs | core | 1,021,996,168 | 5,330 | roonie007 | Duplicated https://github.com/vuejs/vue/pull/2877 and looks like @yyx990803 is not a big fan of it https://github.com/vuejs/vue/pull/2877#issuecomment-226618510.
But having personally tried it with Svelte, it's a very useful feature https://svelte.dev/tutorial/dynamic-attributes | 2022-01-26T09:02:24 | 2022-01-26T09:04:39 | {} | NONE |
vuejs | core | 1,024,432,968 | 5,338 | posva | Duplicate of https://github.com/vuejs/core/issues/3478 | 2022-01-28T17:14:00 | 2022-01-28T17:14:00 | {} | MEMBER |
vuejs | core | 1,020,032,740 | 4,294 | Shinigami92 | Not sure right now, but I may found the solution
```ts
<script lang="ts">
import type { QBtnProps } from 'quasar';
import { defineComponent } from 'vue';
export default defineComponent<QBtnProps>({});
</script>
<template lang="pug">
QBtn(color="primary", flat, icon-right="mdi-chevron-right")
</template>
... | 2022-01-24T12:09:47 | 2022-01-24T12:09:47 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,020,059,263 | 5,274 | cyanxxx | > Your reproduction is not minimal, please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro when reporting a bug. Most bugs should be reproducible with the [SFC Playground](https://sfc.vuejs.org). Try reproducing without quill or router.
https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdD5cbm... | 2022-01-24T12:41:46 | 2022-01-24T12:41:46 | {} | NONE |
vuejs | core | 1,022,536,905 | 4,566 | LinusBorg | Thanks, that's something to work with 👍 | 2022-01-26T19:37:48 | 2022-01-26T19:37:48 | {} | MEMBER |
vuejs | core | 1,022,892,828 | 4,294 | Miofly | any update? | 2022-01-27T06:35:51 | 2022-01-27T07:27:13 | {} | NONE |
vuejs | core | 1,019,927,233 | 5,316 | varHarrie | JS语法问题，相当于执行了unwatch：
```js
watch(/* */)(async function(){/* */}())
```
需要尾随逗号，表示上一语句结束。 | 2022-01-24T10:08:58 | 2022-01-24T10:08:58 | {
"+1": 1
} | NONE |
vuejs | core | 1,021,025,278 | 5,322 | NaincyKumariKnoldus | Hey @hit12369 Can I do this please? | 2022-01-25T10:16:05 | 2022-01-25T10:16:05 | {} | NONE |
vuejs | core | 1,023,317,282 | 5,031 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 35f59b3c2274711cdc0372a4e6258a37b4cd875e
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/61f2b6e257459f00071bd3fc](https://app.netlify.com/sites/vue-sfc-playground/deploys/61f2b6e257459f00071bd3fc)
... | 2022-01-27T15:14:46 | 2022-01-27T15:16:58 | {} | NONE |
vuejs | core | 1,023,990,760 | 5,337 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: e87c843bf53f8aeeddec1b9f2a28ebe68f63cdea
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/61f3a90606d34d0007d38a13](https://app.netlify.com/sites/vue-sfc-playground/deploys/61f3a90606d34d0007d38a13)
... | 2022-01-28T08:27:55 | 2022-01-28T08:30:19 | {} | NONE |
vuejs | core | 1,024,624,886 | 2,027 | bglaz | Are there other known causes of this "Avoid app logic" warning? I am migrating from Vue 2 to 3, and some routes show this warning in the console hundreds, if not thousands of times on one page. | 2022-01-28T20:49:24 | 2022-01-28T20:49:24 | {
"+1": 7
} | NONE |
vuejs | core | 1,019,587,593 | 5,311 | LinusBorg | That API doesn't exist, there is no bug.
If you instead want to propose that we expose the default options for creating a renderer, have a look at what `@vue/runtime-dom` does and exposes, and if you are still missing something, consider opening a discussion in github.com/vuejs/rfcs | 2022-01-23T23:10:02 | 2022-01-23T23:10:02 | {} | MEMBER |
vuejs | core | 1,020,009,113 | 1,342 | umairqazi523 | > Your user doesn't inspect your DOM.
Some of them do. | 2022-01-24T11:40:54 | 2022-01-24T11:40:54 | {} | NONE |
vuejs | core | 1,022,735,576 | 4,294 | richardvanbergen | You can kind-of work around it by exporting only the parts of the interface you need. In this case I only really care about `RouterLinkProps['to']`, I can add the other parts of `RouterLink` as I need them.
```typescript
<script setup lang="ts">
import { RouterLink } from 'vue-router'
import type { RouterLinkProp... | 2022-01-27T00:40:49 | 2022-01-27T00:40:49 | {
"+1": 2
} | NONE |
vuejs | core | 1,022,990,989 | 5,333 | LinusBorg | That's working as intended and also worked like this in Vue 2 already. | 2022-01-27T09:04:54 | 2022-01-27T09:04:54 | {} | MEMBER |
vuejs | core | 1,023,220,225 | 4,344 | ejirocodes | > 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 '@... | 2022-01-27T13:38:51 | 2022-01-27T13:38:51 | {
"+1": 10
} | NONE |
vuejs | core | 1,023,950,774 | 5,336 | LinusBorg | Please read the yellow warning box at the end of that example in the docs again.
Either move the code into a .ts file that does contain some imports or exports or do this in the .d.ts file:
```ts
export {};
declare module "vue" {
export interface ComponentCustomProperties {
$accessor: boolean;
}
}... | 2022-01-28T07:21:11 | 2022-01-28T07:21:11 | {
"+1": 4
} | MEMBER |
vuejs | core | 1,024,232,912 | 5,338 | LinusBorg | This is a Caveat that is not really a bug. the unwrapped interface of a node is:
```ts
// pseudo-name
interface UnwrappedNode {
key: number
checked: boolean
}
```
which is different from the plain Node interface.
The value returned by the `nodes` ref is `UnwrapRef<Node[]>`, not `Node[]`, because it's an ... | 2022-01-28T13:36:43 | 2022-01-28T13:36:43 | {} | MEMBER |
vuejs | core | 1,064,740,882 | 5,567 | ygj6 | https://github.com/vuejs/rfcs/discussions/430 | 2022-03-11T03:37:53 | 2022-03-11T03:37:53 | {} | MEMBER |
vuejs | core | 1,068,060,894 | 3,399 | ShenQingchuan | How is it going so far? I hope we could merge this PR as soon as possible because we actually do not have a comfortable DX experience in template writing.
As
- https://github.com/johnsoncodehk/volar/issues/497
- https://github.com/johnsoncodehk/volar/issues/949
said. | 2022-03-15T14:36:26 | 2022-03-15T14:37:20 | {
"+1": 8
} | CONTRIBUTOR |
vuejs | core | 1,068,078,725 | 4,662 | lroal | Is there any solution for this in sight ? This is a big show stopper in https://github.com/vitejs/vite/issues/5731 | 2022-03-15T14:52:44 | 2022-03-15T14:52:44 | {} | NONE |
vuejs | core | 1,068,460,259 | 5,585 | lidlanca | likely related to
https://github.com/vuejs/core/pull/5118 | 2022-03-15T20:50:05 | 2022-03-15T20:50:05 | {} | CONTRIBUTOR |
vuejs | core | 1,068,528,852 | 5,584 | lidlanca | that is the working alternative.
a prop should technically not be used in v-model since its read-only, but the compiled output can still be more correct.
by referencing via __props in the vmodel logic.
also
`<input v-model="someProp.x" />` will actually compile correctly with __props
which make sense, becau... | 2022-03-15T22:29:26 | 2022-03-15T22:29:26 | {} | CONTRIBUTOR |
vuejs | core | 1,068,843,954 | 5,584 | CherishTheYouth | thank you all, I will modify my codes, best wishes for you two，god kiss you | 2022-03-16T08:07:55 | 2022-03-16T08:07:55 | {} | NONE |
vuejs | core | 1,068,888,415 | 5,593 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 4d3d0d61c2c26af8d69ff48089e2f2ae66911bcb
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/6231a7ae9fb66100087d3e17](https://app.netlify.com/sites/vuejs-coverage/deploys/6231a7ae9fb66100087d3e17)
😎 Browse th... | 2022-03-16T09:02:45 | 2022-03-16T09:07:56 | {} | NONE |
vuejs | core | 1,069,535,820 | 5,594 | mitar | > Why would Vue add classes to an element that is outside of its running scope?
Because it is adding DOM elements to it as well?
> and it can be implemented in userland by looking for the element and adding the classes/attributes.
Hm, everything `Teleport` does could be seen like that, so I could be adding DOM... | 2022-03-16T19:30:16 | 2022-03-16T19:30:16 | {} | NONE |
vuejs | core | 1,064,736,876 | 5,566 | zzzhrookie |
> I think that's normal because you need to state `inheritAttrs: false` in `WrapperInput.vue`.
I think you are right, thanks! @ygj6 | 2022-03-11T03:27:42 | 2022-03-11T03:27:42 | {} | NONE |
vuejs | core | 1,064,941,313 | 5,562 | WormGirl | >
i do not understand, toRefs as intro is to solve reactivity 'disconnected', my problem is toRefs two times the reactivity connect will lose, if just one time, this will work fine. why two times will lose reactivity connect but one time not? | 2022-03-11T09:40:14 | 2022-03-11T09:40:14 | {} | NONE |
vuejs | core | 1,065,123,744 | 5,552 | zscumt123 | @LinusBorg I learned a lot from vuejs, this is my first pr in github, please give me a chance, thx! | 2022-03-11T13:40:35 | 2022-03-11T13:40:35 | {} | CONTRIBUTOR |
vuejs | core | 1,065,206,649 | 5,565 | HcySunYang | @LinusBorg Just use this PR, it's okay, great job. | 2022-03-11T15:15:20 | 2022-03-11T15:15:20 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,067,755,756 | 5,587 | LinusBorg | duplicate of #5525 | 2022-03-15T09:33:35 | 2022-03-15T09:33:35 | {} | MEMBER |
vuejs | core | 1,068,834,394 | 5,135 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 449cfccbc0bee9db13604f49abccbf28b4dc29cf
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/623197b8dfa4cb000847890b](https://app.netlify.com/sites/vue-next-template-explorer/deploys/623... | 2022-03-16T07:54:53 | 2022-03-16T07:55:42 | {} | NONE |
vuejs | core | 1,072,639,282 | 5,602 | talkor | > Why do you expect the component name to be part of the class name?
This was the behavior in vue-cli (https://github.com/vuejs/vue-cli/commit/fd131060db0e35b0f421c7bcd6bb57af63ada2b4) | 2022-03-18T17:36:09 | 2022-03-18T17:36:09 | {} | NONE |
vuejs | core | 1,064,790,632 | 5,568 | netlify[bot] | ❌ Deploy Preview for *vuejs-coverage* failed.
🔨 Explore the source changes: ad2e37931eb676f398f14cd99d795efb82f525b7
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/622ae051f4f8880009865d48](https://app.netlify.com/sites/vuejs-coverage/deploys/622ae051f4f8880009865d48)
| 2022-03-11T05:38:30 | 2022-03-11T05:39:06 | {} | NONE |
vuejs | core | 1,065,778,924 | 5,574 | LinusBorg | > I dont think a framework should be influencing my design choices
That's pretty much what a framework does: it sets a frame in which you can design as you please, but only within the boundaries set by the framework's APIs.
So yes, a framework will be influencing your design choices by its very nature. | 2022-03-12T01:23:18 | 2022-03-12T01:23:18 | {} | MEMBER |
vuejs | core | 1,068,860,239 | 5,591 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 1c18bac9ccb39825cc44405f8c0f0ec426db1f4b
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/62319f7bb6787c0008647da3](https://app.netlify.com/sites/vue-next-template-explorer/deploys/623... | 2022-03-16T08:27:43 | 2022-03-16T08:28:28 | {} | NONE |
vuejs | core | 1,069,397,533 | 5,597 | LinusBorg | This is expected behavior. The order in which child components are created during v-for loops is not guaranteed and depends on the kind of change that is being processed. | 2022-03-16T17:54:08 | 2022-03-16T17:54:08 | {} | MEMBER |
vuejs | core | 1,069,795,389 | 5,597 | NameWjp | This seems to be the default behavior for Vue2, is there an alternative in Vue3？ | 2022-03-17T01:01:31 | 2022-03-17T01:01:31 | {} | NONE |
vuejs | core | 1,070,469,385 | 2,084 | blakjak44 | > Closed, tracking here [vuejs/rfcs#284](https://github.com/vuejs/rfcs/pull/284)
Is there anything holding this up? | 2022-03-17T07:44:59 | 2022-03-17T07:44:59 | {} | NONE |
vuejs | core | 1,071,994,415 | 5,281 | chasegiunta | Checking in on this, as well as wondering if there's any alternative methods available to getting `$attrs` in custom elements? | 2022-03-18T03:31:49 | 2022-03-18T03:31:49 | {} | NONE |
vuejs | core | 1,065,562,864 | 5,572 | LinusBorg | That's expected. The watchEffects run sychonously one after the other, and only then, on the next Tick, will the watch callback be executed. | 2022-03-11T21:50:35 | 2022-03-11T21:50:35 | {} | MEMBER |
vuejs | core | 1,065,330,743 | 5,571 | sudongyuer | > I don't know if it's a bug， so I add warn
Good ~ i think this is a bug.Off topic, are you Chinese? Can you add a friend to communicate with me？ vx:sudongyuer | 2022-03-11T17:32:38 | 2022-03-13T12:47:46 | {} | CONTRIBUTOR |
vuejs | core | 1,066,469,019 | 5,582 | LinusBorg | I think the cumbersome-ness would go away once we have a stable [Reactivity Transform](https://vuejs.org/guide/extras/reactivity-transform.html).
If you still want to add a new API for your usecase, please start a discussion in the [RFC repository](https://github.com/vuejs/rfcs) instead. | 2022-03-14T07:40:17 | 2022-03-14T07:40:17 | {} | MEMBER |
vuejs | core | 1,066,777,019 | 3,258 | SnowingFox | I want to know why this PR are always be opend since it was born? No malice, just want to know | 2022-03-14T13:20:03 | 2022-03-14T13:20:32 | {} | CONTRIBUTOR |
vuejs | core | 1,067,902,988 | 4,891 | WormGirl | > see https://v3.vuejs.org/api/sfc-script-setup.html#defineexpose
>
> [demo](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgdmVyc2lvbiB9IGZyb20gJ3Z1ZSdcbmltcG9ydCBDb21wIGZyb20gJy4vQ29tcC52dWUnXG5jb25zdCBtc2cgPSByZWYoJ0hlbGxvIFdvcmxkJylcbmNvbnN0IGNvbXBvbmVudCA9Q29tcFxuY29uc3QgY29tUmVmP... | 2022-03-15T11:57:19 | 2022-03-15T12:09:05 | {} | NONE |
vuejs | core | 1,068,834,390 | 5,135 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 449cfccbc0bee9db13604f49abccbf28b4dc29cf
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/623197b81a9f2b00089c7201](https://app.netlify.com/sites/vue-sfc-playground/deploys/623197b81a9f2b00089c7201)
... | 2022-03-16T07:54:53 | 2022-03-16T07:57:06 | {} | NONE |
vuejs | core | 1,068,860,244 | 5,591 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 1c18bac9ccb39825cc44405f8c0f0ec426db1f4b
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/62319f7b2855b40009db02b7](https://app.netlify.com/sites/vue-sfc-playground/deploys/62319f7b2855b40009db02b7)
... | 2022-03-16T08:27:43 | 2022-03-16T08:29:50 | {} | NONE |
vuejs | core | 1,068,874,302 | 5,592 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 7d6a97838b701c377a7730bdd55a4a4c1c66eb83
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/6231a3969da2e40008d2c7e1](https://app.netlify.com/sites/vue-next-template-explorer/deploys/623... | 2022-03-16T08:45:14 | 2022-03-16T08:46:13 | {} | NONE |
vuejs | core | 1,069,306,313 | 5,579 | LinusBorg | I must have been sleep-deprived when I wrote my initial reply as none of the the examples in the repo are actually passing pre-rendered vnodes. Sorry.
Will need to take a closer look, but likely, Evan will have to dig into this as this part of the codebase is pretty complex in terms of interactions that are happenin... | 2022-03-16T16:12:58 | 2022-03-16T16:13:37 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,071,069,998 | 5,600 | LinusBorg | What you describe is simply a limitation of the Javascript language. It offers no way for code to be alerted when when other code re-assigns a variable to a new value.
That's basically half of the reason why ref() exists.
If you need support in understanding this, we have a nice community at chat.vuejs.org. If yo... | 2022-03-17T16:44:38 | 2022-03-17T16:44:38 | {} | MEMBER |
vuejs | core | 1,064,790,629 | 5,568 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: ad2e37931eb676f398f14cd99d795efb82f525b7
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/622ae0519de6c20008ccab01](https://app.netlify.com/sites/vue-sfc-playground/deploys/622ae0519de6c20008ccab01)
... | 2022-03-11T05:38:30 | 2022-03-11T05:41:34 | {} | NONE |
vuejs | core | 1,064,834,810 | 5,392 | LinusBorg | @yyx990803 [comment in #5360 that lead to this PR](https://github.com/vuejs/core/issues/5360#issuecomment-1030378628)
Basically, we can drop this check as it simply works without it, and losing it is even necessary to be able to properly key transition-group children. | 2022-03-11T07:07:59 | 2022-03-11T07:07:59 | {} | MEMBER |
vuejs | core | 1,065,571,597 | 5,574 | LinusBorg | It's a design principle that apps are *not* influenced b any global settings, so that potential other apps on the page dnt mess with each other.
You could solve your problem trivially by writing a small wrapper function around createApp that adds that config each time you use it instead of creatApp itself. | 2022-03-11T21:58:39 | 2022-03-11T21:58:39 | {} | MEMBER |
vuejs | core | 1,067,721,696 | 5,586 | Justineo | This can be implemented in userland. You can enforce this pattern in your own codebase.
If you really want to propose a syntax-level change for Vue, it's better to go through the [RFC process](https://github.com/vuejs/rfcs/) to help everybody sort out the pros and cons.
Ps. The number of global HTML attributes (+... | 2022-03-15T08:56:34 | 2022-03-15T08:56:34 | {
"eyes": 1
} | MEMBER |
vuejs | core | 1,068,874,313 | 5,592 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 7d6a97838b701c377a7730bdd55a4a4c1c66eb83
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/6231a3961a22100009bc541c](https://app.netlify.com/sites/vuejs-coverage/deploys/6231a3961a22100009bc541c)
😎 Browse th... | 2022-03-16T08:45:15 | 2022-03-16T08:50:22 | {} | NONE |
vuejs | core | 1,069,375,035 | 5,585 | posva | Your reproduction is not minimal, please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro when reporting a bug. Most bugs should be reproducible with the [SFC Playground](https://sfc.vuejs.org). | 2022-03-16T17:17:53 | 2022-03-16T17:17:53 | {} | MEMBER |
vuejs | core | 1,065,319,177 | 5,573 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 10394176599bd5bf87cfe219db40d6c162637649
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/622b84577accad0008835761](https://app.netlify.com/sites/vue-sfc-playground/deploys/622b84577accad0008835761)
... | 2022-03-11T17:18:19 | 2022-03-11T17:20:23 | {} | NONE |
vuejs | core | 797,365,133 | 2,064 | skirtles-code | Even if the library is being built correctly, it can still fail if you try to include it using `npm link` or a `file:` path in the consuming application. The copy of Vue in the `node_modules` of your library will get pulled in if you include it that way. You can confirm by deleting the `node_modules` folder for the lib... | 2021-03-12T09:34:52 | 2022-03-14T18:49:04 | {
"+1": 16,
"heart": 20,
"hooray": 2
} | CONTRIBUTOR |
vuejs | core | 1,068,860,243 | 5,591 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 1c18bac9ccb39825cc44405f8c0f0ec426db1f4b
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/62319f7b1a9f2b00089d5d64](https://app.netlify.com/sites/vuejs-coverage/deploys/62319f7b1a9f2b00089d5d64)
😎 Browse th... | 2022-03-16T08:27:43 | 2022-03-16T08:33:51 | {} | NONE |
vuejs | core | 1,072,953,485 | 5,575 | a65162 | > Can you add a regression test for this?
Sure. | 2022-03-19T06:32:43 | 2022-03-19T06:32:43 | {} | NONE |
vuejs | core | 1,065,131,252 | 5,546 | edison1105 | the root cause is:
the attribute could not be automatically inherited because component renders as a fragment in prod.
but in DEV, we do a special treatment for `DEV_ROOT_FRAGMENT`.
| 2022-03-11T13:49:53 | 2022-03-11T13:49:53 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,065,319,178 | 5,573 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 10394176599bd5bf87cfe219db40d6c162637649
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/622b84574d88b6000861443b](https://app.netlify.com/sites/vue-next-template-explorer/deploys/622... | 2022-03-11T17:18:19 | 2022-03-11T17:19:06 | {} | NONE |
vuejs | core | 1,067,753,139 | 5,580 | spider4216 | @paraboul thanks for explanation and reference! | 2022-03-15T09:30:46 | 2022-03-15T09:30:46 | {} | NONE |
vuejs | core | 1,066,602,504 | 5,580 | paraboul | This is caused by IME composition as stated in the documentation here : https://vuejs.org/guide/essentials/forms.html#text (see Note about IME).
A workaround is to listen for `@input` event to manually update your ref. This is because non-ascii keyboards (also gboard for autocorrect?) hold the `change` event until c... | 2022-03-14T10:14:24 | 2022-03-15T09:34:39 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 1,068,842,444 | 4,662 | naramdash | @lroal
I use global styles with importing stylesheets in root Component (root.ce.vue) to avoid this problem.
```vue
<style>
// v-bind things... like
--configurable-size: v-bind("~~~")
</style>
<style src="./styles/sheet1"></style> // maybe, use css variables declared in root component style
<style src=".... | 2022-03-16T08:06:02 | 2022-03-16T08:06:02 | {
"+1": 1
} | NONE |
vuejs | core | 1,068,888,367 | 5,593 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 4d3d0d61c2c26af8d69ff48089e2f2ae66911bcb
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/6231a7aea7b45c0009a09d74](https://app.netlify.com/sites/vue-sfc-playground/deploys/6231a7aea7b45c0009a09d74)
... | 2022-03-16T09:02:42 | 2022-03-16T09:04:46 | {} | NONE |
vuejs | core | 1,069,378,446 | 5,594 | posva | Why would Vue add classes to an element that is outside of its running scope? This seems like a very specific use case and it can be implemented in userland by looking for the element and adding the classes/attributes. Usually, you would just add the classes to the `footer` directly, without passing by the `Teleport`. ... | 2022-03-16T17:22:14 | 2022-03-16T17:22:14 | {} | MEMBER |
vuejs | core | 1,071,571,761 | 5,601 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: f4f8dba945df6f183cdd76f584bad7af6d04b8e0
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/6233adb26a7c180008e399eb](https://app.netlify.com/sites/vuejs-coverage/deploys/6233adb26a7c180008e399eb)
😎 Browse th... | 2022-03-17T21:52:53 | 2022-03-17T21:57:56 | {} | NONE |
vuejs | core | 1,072,598,347 | 5,602 | LinusBorg | Why do you expect the component name to be part of the class name? | 2022-03-18T16:51:34 | 2022-03-18T16:51:34 | {} | MEMBER |
vuejs | core | 1,064,728,496 | 5,566 | ygj6 | I think that's normal because you need to state `inheritAttrs: false` in `WrapperInput.vue`. | 2022-03-11T03:10:29 | 2022-03-11T03:10:29 | {} | MEMBER |
vuejs | core | 1,065,784,100 | 5,574 | ryanalbrecht | Point taken.
I should have expressed my thoughts a bit different. In relation to this specific issue. Vue by default handles whitespace differently to browsers and there is no other way to change this other than coming up with a hacky work around. I want to make the design choice of being able change global variable... | 2022-03-12T01:46:28 | 2022-03-12T01:53:41 | {} | NONE |
vuejs | core | 1,066,471,846 | 5,582 | hcg1023 | > I think the cumbersome-ness would go away once we have a stable [Reactivity Transform](https://vuejs.org/guide/extras/reactivity-transform.html).
>
> If you still want to add a new API for your usecase, please start a discussion in the [RFC repository](https://github.com/vuejs/rfcs) instead.
OK, I'll go to [RFC... | 2022-03-14T07:45:11 | 2022-03-14T07:45:11 | {} | CONTRIBUTOR |
vuejs | core | 1,066,447,207 | 5,579 | LinusBorg | Test 2-4 are updating because you pass already-rendered vnodes to the child, instead of a stable slot function.
However, we generally can't give 100% guarantee that all slot functions only re-render in case one of their dependencies changes. The compiler can't always be sure that a slot only depends on its own conte... | 2022-03-14T07:08:16 | 2022-03-14T07:59:10 | {} | MEMBER |
vuejs | core | 1,068,491,111 | 5,584 | LinusBorg | that doesn't create any problems. | 2022-03-15T21:29:44 | 2022-03-15T21:29:44 | {} | MEMBER |
vuejs | core | 1,068,844,405 | 5,584 | CherishTheYouth | @lidlanca @LinusBorg | 2022-03-16T08:08:29 | 2022-03-16T08:08:29 | {} | NONE |
vuejs | core | 1,069,171,738 | 5,596 | LinusBorg | That is not a topic that would be solved in Vue core. Vue core is a library to render interactive UIs, not a code delivery platform or however that thing you have in mind is called.
Someone how actually needs this, could build it though. | 2022-03-16T14:09:30 | 2022-03-16T14:09:30 | {} | MEMBER |
vuejs | core | 1,064,895,956 | 5,555 | pikax | @LinusBorg
Is a bit different, when you are using a `computed` it will be passed as a callback (altho in other cases it doesn't - issue with self accessing `computed`).
[Playground using actual computed](https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbzlApgMwDRwMYXAVxhQBM4BfONKPOAcgDd8VaBuAKDZgE8wU4AxY... | 2022-03-11T08:42:32 | 2022-03-11T08:42:32 | {} | MEMBER |
vuejs | core | 1,064,946,685 | 5,562 | LinusBorg | It's not about "two times". it's about passing the value of the ref to `toRefs`. as soon as `form.value` is assigned another value, your old ref will be referring old state:
```js
const form.value = {
displaySettings: 'whatever'
}
const setForm = toRef(form.value, 'displaySettings')
console.log(setForm.valu... | 2022-03-11T09:46:58 | 2022-03-11T13:53:34 | {} | MEMBER |
vuejs | core | 1,065,932,104 | 5,576 | LinusBorg | That's expected. v-html inserts plain html. You are therefore Limited to the capabilities of plain html.
We don't plan on putting any sort of effort in extending v-html capabilities. It's an escape hedge for edge cases, not a central feature. | 2022-03-12T18:03:14 | 2022-03-12T18:03:14 | {} | MEMBER |
vuejs | core | 1,068,874,309 | 5,592 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 7d6a97838b701c377a7730bdd55a4a4c1c66eb83
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/6231a39629bbdb0008f4756f](https://app.netlify.com/sites/vue-sfc-playground/deploys/6231a39629bbdb0008f4756f)
... | 2022-03-16T08:45:15 | 2022-03-16T08:47:15 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.