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 | 706,471,989 | 2,339 | tangjinzhou | @posva @underfin
I changed the bug to a feature request.
I don't think this is a reasonable design and I hope to modify this default behavior.
Especially when there are multiple types. | 2020-10-10T02:34:21 | 2020-10-10T04:17:28 | {} | CONTRIBUTOR |
vuejs | core | 706,508,008 | 2,347 | skirtles-code | It'd be inconsistent between builds too as production builds strip out comments:
**vue.global.js:** https://jsfiddle.net/skirtle/q78raL1z/1/
**vue.global.prod.js:** https://jsfiddle.net/skirtle/q78raL1z/ | 2020-10-10T08:01:21 | 2020-10-10T08:01:21 | {} | CONTRIBUTOR |
vuejs | core | 703,340,607 | 2,297 | 69hunter | @posva Thanks, I will do so. | 2020-10-05T00:39:14 | 2020-10-05T00:39:14 | {} | CONTRIBUTOR |
vuejs | core | 704,383,196 | 2,312 | unbyte | The way you switch themes should be done by yourself, not Vue. There are already many implementations. | 2020-10-06T16:04:11 | 2020-10-06T16:04:11 | {} | CONTRIBUTOR |
vuejs | core | 704,810,901 | 2,325 | posva | We fixed this problem on Vue 2, so it makes sense to have it as well. I suppose `min`, `max`, and `step` have to be set before the value | 2020-10-07T09:25:03 | 2020-10-07T09:25:03 | {
"+1": 1
} | MEMBER |
vuejs | core | 705,271,501 | 2,291 | yyx990803 | As a workaround, use a post flush watcher:
```js
watch: {
"$route.params.fooId": {
handler: "fetch",
flush: "post"
}
}
``` | 2020-10-08T01:03:34 | 2020-10-08T01:03:34 | {
"+1": 8,
"heart": 1
} | MEMBER |
vuejs | core | 706,181,279 | 2,343 | robaxelsen | @LinusBorg Thanks for having a look and providing insights!
> Interested to understand how React et. al. void this.
They don't handle it, I am afraid. From [https://custom-elements-everywhere.com/](https://custom-elements-everywhere.com/): "React passes all data to Custom Elements in the form of HTML attributes. ... | 2020-10-09T13:29:33 | 2020-10-09T13:32:23 | {} | NONE |
vuejs | core | 706,353,884 | 2,338 | wxk6b1203 | Yet another reproduction
Version
3.0.0-0
Reproduction link
https://gist.github.com/wxk6b1203/66914efbb633897655f525af9e4f3140
What is expected?
The default value specification at L 33 could be omitted.
What is actually happening?
If the default value at L 33 was deleted, the `computed` below shows that ... | 2020-10-09T19:04:37 | 2020-10-09T19:04:37 | {
"+1": 1
} | NONE |
vuejs | core | 703,299,047 | 2,297 | posva | Thanks but if you want to suggest extra changes to the existing PR, please do so by reviewing the existing one: https://github.com/vuejs/vue-next/pull/2254 | 2020-10-04T18:50:44 | 2020-10-04T18:50:44 | {} | MEMBER |
vuejs | core | 705,291,541 | 2,306 | edison1105 | Maybe it fixed via f06518a8c9201b4fa2a956595aa9d89a192fcd20
I tested it work fine, So I closed my PR #2310 | 2020-10-08T02:23:43 | 2020-10-08T02:23:43 | {} | MEMBER |
vuejs | core | 706,500,050 | 2,339 | posva | Please check existions issues on vue 2 repo first and if it still makes sense to you open a proper RFC | 2020-10-10T06:54:39 | 2020-10-10T06:54:39 | {} | MEMBER |
vuejs | core | 706,836,914 | 2,356 | edison1105 | 最好去 vue-router-next 仓库下去提 issues | 2020-10-12T03:31:46 | 2020-10-12T03:31:46 | {} | MEMBER |
vuejs | core | 703,558,276 | 1,600 | nfplee | Any news on when this? This causes a problem for me as I render my code on the server (for SEO purposes) and then parse it with Vue which then changes the white-space and causes multiple issues. I'm going to hold out from upgrading until this issue is resolved. | 2020-10-05T10:58:57 | 2020-10-05T10:58:57 | {
"+1": 5
} | NONE |
vuejs | core | 703,989,027 | 2,303 | langhuihui | ```
createServer({
alias: {
vue: "vue/dist/vue.esm-bundler.js"
},
cssPreprocessOptions: {
less: {
javascriptEnabled: true,
},
},
configureServer: [myPlugin]
}).listen(3000)
```
我配置了，但是没有效果 | 2020-10-06T02:20:54 | 2020-10-06T02:20:54 | {} | NONE |
vuejs | core | 704,470,008 | 2,312 | 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). | 2020-10-06T18:33:26 | 2020-10-06T18:33:26 | {} | MEMBER |
vuejs | core | 705,547,659 | 2,333 | unbyte | @LinusBorg have tested on latest version https://github.com/vuejs/vue-next/tree/fbd198fbfe2f87c3c15a63d9770d00bf3fc9c142 , child element is hidden correctly | 2020-10-08T12:53:56 | 2020-10-08T12:53:56 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 706,604,521 | 2,336 | yyx990803 | Thanks for the PR but I don't think this is the right fix. See https://github.com/vuejs/vue-next/commit/2ae3b26679faf2d5393998ba806b99748679195a | 2020-10-10T20:07:52 | 2020-10-10T20:08:10 | {} | MEMBER |
vuejs | core | 706,662,938 | 2,250 | KaelWD | You'd use `{ [key: string]: Prop }` or `ComponentPropsOptions` for that. | 2020-10-11T07:24:31 | 2020-10-11T07:24:31 | {
"hooray": 1
} | CONTRIBUTOR |
vuejs | core | 706,727,283 | 2,303 | unbyte | @langhuihui 有没有最小复现项目 | 2020-10-11T16:07:31 | 2020-10-11T16:07:31 | {} | CONTRIBUTOR |
vuejs | core | 706,802,314 | 2,250 | bhabgs | 谢谢 | 2020-10-12T01:04:00 | 2020-10-12T01:04:00 | {} | NONE |
vuejs | core | 706,828,089 | 2,358 | Justineo | 请提供所描述问题的最小化重现。参见[这里](https://new-issue.vuejs.org/?repo=vuejs/vue&lang=zh-cn#why-repro)。 | 2020-10-12T03:00:56 | 2020-10-12T03:00:56 | {} | MEMBER |
vuejs | core | 703,463,292 | 2,296 | posva | See how it is done on vue-router-next: https://github.com/vuejs/vue-router-next/blob/master/src/globalExtensions.ts
It's worth checking vuejs/docs-next repository for open issues about documenting this and open a new one if there is none to discuss and propose things | 2020-10-05T07:47:57 | 2020-10-05T07:47:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 703,881,839 | 2,281 | smilingkite | Ok, let me see if I've got this right.
In the setup method I've set a variable 'nonReactiveCount' to 0. Its value gets exported to the vue-instance as the value of the exported 'nonReactiveCount' key. It's not reactive.
I can increment this.nonReactiveCount through the methods, because it's available on the 'thi... | 2020-10-05T20:51:46 | 2020-10-05T20:57:31 | {} | NONE |
vuejs | core | 705,139,005 | 2,293 | yyx990803 | We can definitely optimize this but I wouldn't consider it a bug. | 2020-10-07T19:12:58 | 2020-10-07T19:12:58 | {} | MEMBER |
vuejs | core | 705,277,836 | 2,138 | Gkxie | > Why else it would have to trigger then? The code itself is recursive: an effect that mutates its own dependency. It is recursive in Vue 2 and I don't see any reason why it shouldn't be that way in Vue 3.
**example 1**
```javascript
const arr = reactive([])
watchEffect(()=>{
arr.push(1)
})
watchEffect(()=>{... | 2020-10-08T01:29:37 | 2020-10-08T01:30:38 | {
"-1": 1
} | NONE |
vuejs | core | 705,787,097 | 2,333 | yyx990803 | yeah, fixed by 4d1ebb5deb4c1cb2a02e8482bf8f9cc87197b088 | 2020-10-08T19:50:09 | 2020-10-08T19:50:09 | {} | MEMBER |
vuejs | core | 706,358,966 | 2,343 | graynorton | It seems significant that the "vanilla" custom element doesn't exhibit the same behavior–this would seem to point to a problem in Stencil.
I confirmed that a vanilla element seems to work fine here: https://stackblitz.com/edit/vue-rxb2du?file=src%2FApp.vue
Notably, it wasn't even necessary to use `.prop` in the b... | 2020-10-09T19:16:10 | 2020-10-09T19:16:10 | {} | NONE |
vuejs | core | 706,525,135 | 2,343 | KaelWD | Vue just uses `key in el` to determine if it should bind to a property: https://github.com/vuejs/vue-next/blob/51c18ed193285b593adbf909bf323a645de246e7/packages/runtime-dom/src/patchProp.ts#L112
Stencil doesn't define the `data` property until after vue has already checked if it exists: https://github.com/ionic-team... | 2020-10-10T10:13:10 | 2020-10-11T07:31:30 | {
"+1": 5
} | CONTRIBUTOR |
vuejs | core | 706,696,484 | 2,353 | posva | Isn't this a bit overkill though? Maybe looking through the vnode attrs to check if the value needs to be set one tick after instead of using mounted like in https://github.com/vuejs/vue-next/commit/54ed7592e416fc411196e9b767aebcc4f2ca20d8 works | 2020-10-11T12:18:47 | 2020-10-11T12:18:47 | {} | MEMBER |
vuejs | core | 706,746,652 | 2,355 | LinusBorg | > Is this behaviour expected?
Yes. In the original example, you essentially bind the setTimeout's callback to the original instance's `this`, before the proxy exists. That means the mutation done by the callback is done on the original object, not the proxy.
In the workaround, you do it in a method called _thro... | 2020-10-11T18:25:21 | 2020-10-11T18:29:34 | {
"+1": 1
} | MEMBER |
vuejs | core | 706,972,637 | 2,343 | johnjenkins | Stencil manages the loading of components and by default it does so lazily.
@KaelWD comment makes sense. I suspect if you were to change to a custom element with no lazy-loading it'd work fine (https://stenciljs.com/docs/custom-elements) | 2020-10-12T08:38:59 | 2020-10-12T09:54:01 | {
"+1": 2
} | NONE |
vuejs | core | 703,445,263 | 2,296 | ux-engineer | @posva is there an official guideline for this question though (if no, this should be a feature request)?
As Evan stated in your linked code review: "There's no way to make this work in TS though. If users insist on using this with TS they'd have to shim the types themselves." | 2020-10-05T07:10:46 | 2020-10-05T07:10:46 | {
"+1": 2,
"eyes": 1,
"rocket": 1
} | NONE |
vuejs | core | 704,532,882 | 2,314 | neryams | I created this PR, which fixes the issue in my local project https://github.com/vuejs/vue-next/pull/2315 | 2020-10-06T20:25:10 | 2020-10-06T20:25:10 | {} | NONE |
vuejs | core | 704,722,656 | 2,321 | LinusBorg | We already support JSX. We will no invent a new kind of JSX for Vue and thus introduce a third template syntax. | 2020-10-07T06:25:06 | 2020-10-07T06:25:06 | {
"+1": 1
} | MEMBER |
vuejs | core | 705,294,987 | 2,306 | yyx990803 | fixed by f06518a | 2020-10-08T02:37:20 | 2020-10-08T02:37:20 | {} | MEMBER |
vuejs | core | 705,394,818 | 2,332 | posva | Always provide boiled down reproductions when reporting bugs. Here is an example: https://jsfiddle.net/w54fzat2/. Open a new issue once you manage to boil down the reproduction | 2020-10-08T07:47:00 | 2020-10-08T07:47:00 | {} | MEMBER |
vuejs | core | 705,996,222 | 2,339 | underfin | This is expected behavior as same as v2. | 2020-10-09T06:28:40 | 2020-10-09T06:28:40 | {
"+1": 1
} | MEMBER |
vuejs | core | 706,712,596 | 2,353 | posva | I meant reading from `vnode.props` the possible attributes like type, min, max and range, and set them on the element before setting the value. For example, doing a rough `Object.assign(el, vnode.props)` before `el.value = value` solves the issue
> I've also considered a less general solution with no runtime cost, t... | 2020-10-11T14:26:25 | 2020-10-11T14:26:25 | {} | MEMBER |
vuejs | core | 706,945,366 | 2,347 | qmhc | It doesn't work when I want to multiple pass slot between components.
```html
<!-- foo.vue -->
<template>
<div class="foo">
<slot :value="value"> current value: {{ value }} </slot>
<button @click="value += 1">Add</button>
</div>
</template>
<!-- baz.vue -->
<template>
<div class="baz">
... | 2020-10-12T07:52:00 | 2020-10-12T07:52:00 | {} | NONE |
vuejs | core | 661,806,878 | 1,657 | cuixiaorui | I want to be clear here
There are two cases in VTU when using functional Component
The first case is:
Functional Component is called at mount time
```js
const Foo = (props,ctx)=>{
return h("div","foo")
}
const wrapper = mount(Foo)
```
In that case, we should be able to handle ctx.emit while passing... | 2020-07-21T11:46:00 | 2020-07-21T11:46:25 | {} | CONTRIBUTOR |
vuejs | core | 663,375,293 | 1,686 | njleonzhang | @onmyflow according to my understanding, wrong key would cause functional issue, undefined key should not cause functional issue. | 2020-07-24T06:56:37 | 2020-07-24T06:56:52 | {} | NONE |
vuejs | core | 663,532,129 | 1,697 | pikax | Make sure the repo is not private! | 2020-07-24T13:14:00 | 2020-07-24T13:14:00 | {} | MEMBER |
vuejs | core | 663,912,280 | 1,711 | posva | This is expected because you are modifying the array and it's copied by reference in JavaScript. So `oldValue === newValue` | 2020-07-25T22:26:06 | 2020-07-25T22:26:06 | {
"+1": 1
} | MEMBER |
vuejs | core | 663,192,153 | 1,682 | RobbinBaauw | @yyx990803 I believe that with the `proxyRefs `and the unref in the component proxy, the "first and last" layers of a nested object are unreffed. This is because everything returned from the component proxy can just be unreffed.
I don't have access to a pc currently though, so I'm not 100% sure, however iirc somethin... | 2020-07-23T19:31:53 | 2020-07-23T19:31:53 | {} | CONTRIBUTOR |
vuejs | core | 663,757,475 | 1,701 | Picknight | Your vue.js version seems to be `3.0.0-alpha.1`, because:
I use version `3.0.0-rc.3` work fine.
 {},
set foo() {}
})
```
Or - create a Proxy around your raw object first, then pass your proxy to `reactive`. This ensures the final reactive proxy is still a Vue proxy. | 2020-07-27T20:51:38 | 2020-07-27T20:51:38 | {} | MEMBER |
vuejs | core | 661,905,620 | 1,609 | yyx990803 | Did you check the console? Any errors?
Works properly on Safari 13.1. It's going to be tough to find a machine with the right Safari version :/
Also - it seems you are using beta.15 which is quite outdated, try rc.2. | 2020-07-21T14:45:48 | 2020-07-21T14:46:26 | {} | MEMBER |
vuejs | core | 662,243,778 | 1,672 | znck | Yes, it was intentional. | 2020-07-22T05:07:32 | 2020-07-22T05:07:32 | {} | MEMBER |
vuejs | core | 662,470,927 | 1,681 | ByScripts | When using `<h1 ref="titleEl">`, it gives us the sensation of returning an unused property from `setup()`. | 2020-07-22T14:01:21 | 2020-07-22T14:02:02 | {} | NONE |
vuejs | core | 663,848,918 | 1,696 | posva | See https://github.com/vuejs/rfcs/blob/master/active-rfcs/0009-global-api-change.md#mounting-behavior-difference-from-2x | 2020-07-25T12:16:29 | 2020-07-25T12:16:29 | {} | MEMBER |
vuejs | core | 663,849,543 | 1,705 | posva | Please check the console log:
```
[Vue warn]: Failed to locate Teleport target with selector ".cell2". Note the target element must exist before the component is mounted - i.e. the target cannot be rendered by the component itself, and ideally should be outside of the entire Vue component tree.
at <App>
```
... | 2020-07-25T12:23:19 | 2020-07-25T12:23:19 | {} | MEMBER |
vuejs | core | 664,994,360 | 1,727 | eddeisling | Thank you for response. Yeah, sync will be working.
But nevertheless, I can understand why there is no 2 logs per click, but it is weird that watch do not work at all after ref is changed. It means that it is forbidden to change watched ref in watch callback?
If it is expected behaviour, feel free to close the issu... | 2020-07-28T11:49:52 | 2020-07-28T11:49:52 | {} | NONE |
vuejs | core | 665,177,708 | 1,700 | yyx990803 | This is expected behavior.
Directives are meant for DOM manipulations. When they are used on a component, they fallthrough like attributes (e.g. `class` and `style`) to the root of the component's sub tree. In this case, the `vnode` you are getting is the vnode representing the child component's root element, not th... | 2020-07-28T17:38:11 | 2020-07-28T17:38:11 | {
"+1": 1
} | MEMBER |
vuejs | core | 665,198,231 | 1,724 | yyx990803 | The root cause of #1704 is because `v-if` in off state renders a comment node, which is then mistakenly filtered out as a user comment when trying to determine fallthrough target in a fragment root with user comments. See 355c0526
This fix should be unnecessary since in compiled output `cloneVNode` should only happe... | 2020-07-28T18:18:25 | 2020-07-28T18:18:25 | {} | MEMBER |
vuejs | core | 665,232,604 | 1,717 | yyx990803 | Thanks for the PR but the correct fix should be inside the renderer. See https://github.com/vuejs/vue-next/pull/1703 | 2020-07-28T19:28:41 | 2020-07-28T19:28:41 | {} | MEMBER |
vuejs | core | 665,342,715 | 1,518 | eolme | > why not use vue-router hooks
Why do I need vue-router to switch 2 components? | 2020-07-28T23:19:19 | 2020-07-28T23:19:19 | {} | CONTRIBUTOR |
vuejs | core | 665,655,391 | 1,734 | leopiccionia | Another problem with same root cause, now using `v-if` inside `<transition>`: #1730.
I suppose a solution for some cases is using `<template v-if>`, probably.
But nesting `v-if` inside `v-for` is an ubiquitous pattern. It may be one of the biggest breaking changes in Vue 3. | 2020-07-29T13:12:35 | 2020-07-29T13:13:16 | {} | CONTRIBUTOR |
vuejs | core | 665,700,368 | 1,734 | IonianPlayboy | I tried wrapping the `v-if` element inside a `<template>` and to put the `v-if` on the `<template>` and it removed the warning.
However, the added `<template>` makes the code look more convoluted and is less readable.
Instead of having :
```vue
<template v-for="({id, text}, index) in items">
<span :key="'tex... | 2020-07-29T14:31:54 | 2020-07-29T14:33:27 | {} | NONE |
vuejs | core | 661,711,381 | 1,657 | LinusBorg | > Is there a good way to know if a component is functional?
shouldn't `typeof component === 'function'` suffice?
..well, not for async components :/ | 2020-07-21T08:22:09 | 2020-07-21T08:22:09 | {} | MEMBER |
vuejs | core | 661,724,758 | 1,532 | vmihailenco | composition-api has a solution for this under name `activateCurrentInstance` https://github.com/vuejs/composition-api/blob/01524a4e4114cbb9443b6d697acb4cfa39f27700/src/utils/instance.ts#L101-L119 . It is private and only changes current instance in composition-api, but the idea is the same.
>are wrappers around the ... | 2020-07-21T08:49:08 | 2020-07-21T08:51:51 | {} | NONE |
vuejs | core | 662,768,461 | 1,682 | yyx990803 | Auto un-ref is mostly an ergonomic need at the root level, because it is only at the root level you are likely to get a mix of plain objects, reactive objects and refs.
- For root level refs, the behavior is exactly the same as before.
- For reactive objects, the behavior is also exactly the same as before. These a... | 2020-07-23T00:50:34 | 2020-07-23T00:53:25 | {} | MEMBER |
vuejs | core | 663,181,480 | 1,682 | yyx990803 | @RobbinBaauw I may be mistaken but your approach doesn't seem to do deep unwrap (i.e. `object.nestedRef` will still be a ref in templates). The `unref` is also only called for root level properties in `setupState`. Also unwrapping in instance proxies won't account for direct field access. | 2020-07-23T19:07:33 | 2020-07-23T19:08:04 | {} | MEMBER |
vuejs | core | 663,309,309 | 1,687 | mmis1000 | So, the proper way to do this is.
Create your own compiler like compiler-dom, and inject the compiler into vue-loader via the vue.config.js?
Like
vue.config.js
```js
const vuePluginNext = require.resolve('vue-cli-plugin-vue-next')
const vueLoaderNext = require.resolve('vue-loader', {paths: [vuePluginNext] })... | 2020-07-24T01:28:15 | 2020-07-24T05:07:39 | {} | CONTRIBUTOR |
vuejs | core | 663,531,611 | 1,697 | posva | if you open an issue provide a reproduction. This issue's reproduction points to a 404 | 2020-07-24T13:12:49 | 2020-07-24T13:12:49 | {} | MEMBER |
vuejs | core | 663,573,436 | 1,696 | mannok | There isn't `this` in Vue 3 | 2020-07-24T14:42:51 | 2020-07-24T14:42:51 | {
"-1": 2
} | NONE |
vuejs | core | 661,744,889 | 1,648 | lexSeven | ok, what ever... | 2020-07-21T09:27:23 | 2020-07-21T09:27:23 | {} | CONTRIBUTOR |
vuejs | core | 661,896,745 | 1,661 | yyx990803 | I was thinking about this when reading that thread! However I think it should be supported in both dev and prod, since `name` can lead to behavior differences for recursive components (components referencing themselves in templates). | 2020-07-21T14:30:38 | 2020-07-21T14:30:38 | {
"+1": 2
} | MEMBER |
vuejs | core | 661,913,402 | 1,609 | posva | @yyx990803 I reproduced it through BrowserStack. This is the stack trace
| 2020-07-21T14:59:05 | 2020-07-21T14:59:05 | {} | MEMBER |
vuejs | core | 662,239,383 | 1,674 | wxy0902 | https://developer.mozilla.org/zh-CN/docs/Web/HTML/Element/big | 2020-07-22T04:50:46 | 2020-07-22T04:50:46 | {} | CONTRIBUTOR |
vuejs | core | 663,356,910 | 1,686 | dnlsndr | @njleonzhang As far as I remember, vue2 had the same issue. If you didn't set the :key, you'd sometimes get really strange behaviour when mutating the looped list.
So it's not only a performance issue, but rather a issue that emerges when not using the suggested :key prop. | 2020-07-24T05:44:44 | 2020-07-24T05:44:44 | {} | NONE |
vuejs | core | 665,745,971 | 1,734 | yyx990803 | This is expected - in v3 `<template v-for>` compiles into a list of fragment nodes so the key should be on the `<template>` instead of the elements inside. | 2020-07-29T15:50:31 | 2020-07-29T15:50:31 | {
"+1": 4
} | MEMBER |
vuejs | core | 666,236,328 | 1,409 | icehaunter | I came across the same issue where I'd like to fetch some data in the root component (displaying global loader is fine at that point), and I'd like to provide the fetched data (as it is, essentially, a dictionary) to all child components - they need that dictionary to properly display some data. | 2020-07-30T08:49:32 | 2020-07-30T08:49:32 | {
"+1": 3
} | NONE |
vuejs | core | 662,030,961 | 1,671 | yyx990803 | In Vue 3 we strongly recommend against mixins and will not be investing more efforts into facilitating composition patterns that revolve around inheritance/mixins/HOCs. Of course, you are welcome to use whatever patterns you like, but you likely won't receive much feedback from us.
Composition API is designed exactl... | 2020-07-21T18:26:46 | 2020-07-21T18:29:32 | {
"+1": 2
} | MEMBER |
vuejs | core | 662,741,141 | 1,682 | jods4 | > We have went back-and-forth on this behavior during the alpha/beta phases.
Yup this was discussed at great lengths during the alpha, so I'm a bit surprised by the late change!
I think we established that with proxies there will always be unfortunate edge cases but there were 2 "safer" patterns:
- make everythi... | 2020-07-22T23:07:14 | 2020-07-22T23:07:14 | {} | CONTRIBUTOR |
vuejs | core | 663,758,870 | 1,700 | Picknight | > Anyway I've tried to add a prop: nothing changes.
I tried it and it work fine. | 2020-07-24T22:28:33 | 2020-07-24T22:28:33 | {
"-1": 6
} | CONTRIBUTOR |
vuejs | core | 663,833,676 | 1,701 | visualjerk | Indeed, it does :smile:
Thanks for the hint! | 2020-07-25T09:25:20 | 2020-07-25T09:25:20 | {} | NONE |
vuejs | core | 662,051,830 | 1,672 | yyx990803 | This will only allow use of it when calling `generate` in TS - is that intentional? (which I think is ok since this should be considered internal API) | 2020-07-21T19:07:57 | 2020-07-21T19:07:57 | {} | MEMBER |
vuejs | core | 662,916,811 | 1,686 | dnlsndr | I believe that's because you are not using the key property in the v-for e.g.: `:key="item.name"`
Not using the key property can lead to such problems.
I tried it with `:key="item.name"`, it works for me. | 2020-07-23T09:48:50 | 2020-07-23T09:50:09 | {
"+1": 1
} | NONE |
vuejs | core | 664,085,752 | 1,539 | gliheng | Run into this issue recently. It's really unexpected. vue2 works well though. | 2020-07-27T02:26:35 | 2020-07-27T02:26:35 | {} | NONE |
vuejs | core | 664,205,472 | 1,715 | posva | In your example your Hello component is using v-model but it should just pass a prop since it's not modifying its `modelValue` prop. Otherwise you have to provide the `inheritAttrs: false` option to it so it doesn't inherit the binding and event listener from its parent and put it on the Test component, which conflict ... | 2020-07-27T08:40:49 | 2020-07-27T08:40:49 | {
"eyes": 1
} | MEMBER |
vuejs | core | 665,116,064 | 1,722 | yyx990803 | See https://github.com/vuejs/docs-next/commit/1aa17921ddcf5cfb57fbeca73bfceb8fcdd61f70 | 2020-07-28T15:42:04 | 2020-07-28T15:42:04 | {} | MEMBER |
vuejs | core | 662,812,514 | 1,682 | RobbinBaauw | Wow!
This looks great, but it may be possible to improve it even more: I made an implementation of something similar as an experiment, and the nested auto unref also worked there. It was done by also unreffing in the component proxy (https://github.com/RobbinBaauw/vue-next/commit/d4653a98782e1ec616fc68a03a6761585b20e... | 2020-07-23T04:27:15 | 2020-07-23T04:30:16 | {} | CONTRIBUTOR |
vuejs | core | 662,919,947 | 1,686 | posva | This is one of the cases where using a `key` is important so Vue can properly reuse the correct DOM elements. Otherwise they get reused in the wrong order and they preserve their DOM state | 2020-07-23T09:57:18 | 2020-07-23T09:57:18 | {} | MEMBER |
vuejs | core | 663,768,701 | 1,700 | jfet97 | @Picknight could you provide a codesandbox like I did? You can fork mine as well.
Because mine contradics what you are saying, but perhaps you are using a different version of Vue 3 or you are doing something different.
Thanks 🙂 | 2020-07-24T23:11:45 | 2020-07-24T23:11:45 | {} | NONE |
vuejs | core | 666,290,328 | 1,738 | posva | Thank you but the first parameter is necessary here. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map/forEach | 2020-07-30T10:41:56 | 2020-07-30T10:41:56 | {} | MEMBER |
vuejs | core | 662,941,090 | 1,686 | njleonzhang | OK，I haven't set key, so every node should be patched, which a performance issue in vue2. in vue3, it cause incorrect render, should we consider this as a bug? | 2020-07-23T10:52:40 | 2020-07-23T10:54:45 | {} | NONE |
vuejs | core | 665,105,669 | 1,703 | yyx990803 | This failing test actually exposed some issues regarding the handling of Teleport children in block tree mode. The main reason is that its direct children needs to always inherit `vnode.el` from previous children so that they can be moved later, but it is sometimes skipped in block tree mode. | 2020-07-28T15:23:22 | 2020-07-28T15:23:22 | {
"+1": 1
} | MEMBER |
vuejs | core | 665,177,870 | 1,710 | yyx990803 | See https://github.com/vuejs/vue-next/issues/1700#issuecomment-665177708
`vnode.component` should only be non-null on actual component vnodes. | 2020-07-28T17:38:34 | 2020-07-28T17:38:34 | {} | MEMBER |
vuejs | core | 665,510,995 | 1,712 | eddeisling | @yyx990803 hello, could you explain please how i need to use v-if-else inside v-for?
```html
// eslint error: vue/require-v-for-key
<template v-for="item of items">
<div v-if="item"><div>
<span v-else></span>
</template>
// eslint error: vue/no-template-key
<template v-for="item of items" :key="item">
... | 2020-07-29T08:15:27 | 2020-07-29T08:18:19 | {} | NONE |
vuejs | core | 666,585,124 | 1,594 | 509dave16 | @AlexandreBonaventure You might need to also forward `scopedSlots`. | 2020-07-30T18:29:45 | 2020-07-30T18:29:45 | {} | NONE |
vuejs | core | 662,298,144 | 1,674 | posva | Deprecated properties should still be kept in types. If anything, they should be marked as deprecated with `@deprecated` | 2020-07-22T07:43:11 | 2020-07-22T07:43:11 | {
"+1": 1
} | MEMBER |
vuejs | core | 662,487,879 | 1,681 | posva | This was discussed over at https://github.com/vuejs/rfcs/pull/78 on the _Template refs_ section. Having a string also allows dynamic refs. | 2020-07-22T14:31:18 | 2020-07-22T14:31:18 | {} | MEMBER |
vuejs | core | 663,176,535 | 1,687 | yyx990803 | You don't need to implement `insertStaticContent` - it's only used if the accompanying compiler for your target platform leverages static string transforms:
- `compiler-core` by default doesn't perform stringify optimizations
- `compiler-dom` implements an extra transform adjacent static content into `Static` nodes... | 2020-07-23T18:57:11 | 2020-07-23T18:57:11 | {
"eyes": 1
} | MEMBER |
vuejs | core | 663,465,553 | 1,695 | pikax | you can use [customRef](https://v3.vuejs.org/api/refs-api.html#customref) | 2020-07-24T10:05:06 | 2020-07-24T10:05:06 | {
"+1": 1
} | MEMBER |
vuejs | core | 663,532,786 | 1,697 | yoyoys | @posva @pikax I've just make repo public right now, thanks. | 2020-07-24T13:15:24 | 2020-07-24T13:15:24 | {} | NONE |
vuejs | core | 663,574,633 | 1,696 | Araozu | I believe your code is incorrect. When you use `this.$el` you get the DOM element managed by Vue, not the div#app. So, in your code, `this.$el` refers to the div in your template:
```
template: `
<div> <!-- This div is this.$el -->
<h1>{{title}}</h1>
</div>
`,
```
And secondly, you can't ... | 2020-07-24T14:45:08 | 2020-07-24T14:45:45 | {
"+1": 1
} | NONE |
vuejs | core | 661,722,466 | 1,664 | posva | There is no warning... | 2020-07-21T08:44:51 | 2020-07-21T08:44:51 | {} | MEMBER |
vuejs | core | 663,421,117 | 1,682 | basvanmeurs | > 1. This change is targeted at people who have non-proxy objects in their graph (something we said we would discourage).
**Why is this a serious problem that must be resolved?**
We have an application in which we use a datamodel (classes with properties and methods) and tend to provide these in the setup context... | 2020-07-24T08:50:46 | 2020-07-24T08:50:46 | {
"+1": 4
} | CONTRIBUTOR |
vuejs | core | 663,828,870 | 1,700 | briosheje | I can confirm that `component` seems to be null on chrome 84.0.4147.89 and also has the same behavior in firefox.
Perhaps should this be marked as a possible regression issue? | 2020-07-25T08:34:34 | 2020-07-25T08:34:34 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.