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 | 776,516,958 | 3,214 | posva | https://v3.vuejs.org/guide/migration/events-api.html#overview | 2021-02-10T07:55:03 | 2021-02-10T07:55:03 | {} | MEMBER |
vuejs | core | 776,538,896 | 3,104 | HcySunYang | When toggling branches with in-out mode, the branch being entered maybe a comment node, which makes the transition invalid and never completes. [this](https://github.com/vuejs/vue-next/pull/3109) PR checks the type of node being entered. | 2021-02-10T08:38:38 | 2021-02-10T08:38:38 | {} | MEMBER |
vuejs | core | 776,695,257 | 3,216 | HcySunYang | Thank you for your interest, but this is a breaking change and does not seem reasonable. In addition, at this stage, any new features need to go through [RFCs](https://github.com/vuejs/rfcs).
BTW: You can easily implement a custom directive like `v-outer-html` | 2021-02-10T13:10:08 | 2021-02-10T13:10:08 | {} | MEMBER |
vuejs | core | 778,629,772 | 3,229 | posva | Yes, you need a data property. You can create a composable to handle it. I created a mixin with Vue 2 in mind to handle this case: https://github.com/posva/vue-prop-data-fallback
| 2021-02-13T14:52:13 | 2021-02-13T14:52:13 | {
"heart": 1
} | MEMBER |
vuejs | core | 775,699,251 | 3,204 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/12202?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Dependabot will still automatically merge this pull request if you amend it and your tes... | 2021-02-09T06:17:56 | 2021-02-09T06:17:56 | {} | CONTRIBUTOR |
vuejs | core | 776,751,892 | 3,211 | guillenotfound | Is there any workaround while the MR gets merged? | 2021-02-10T14:38:50 | 2021-02-10T14:38:50 | {} | NONE |
vuejs | core | 777,225,676 | 3,222 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.56 KB (0%) |
| runtime-dom.global.prod.js | 26.95 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-11T06:15:30 | 2021-02-11T06:15:30 | {} | NONE |
vuejs | core | 775,336,122 | 3,070 | Akryum | I've taken some parts of #2902 to make it work like a lifecycle hook. Do we merge this PR into @tabjy's PR to give him credits? | 2021-02-08T18:06:01 | 2021-02-08T18:06:01 | {} | MEMBER |
vuejs | core | 775,602,023 | 3,199 | HcySunYang | You can use v-model until this gets fixed, https://codesandbox.io/s/angry-sound-ljjte?file=/src/App.vue | 2021-02-09T02:10:43 | 2021-02-09T02:10:43 | {} | MEMBER |
vuejs | core | 776,464,085 | 3,199 | HcySunYang | The `children` are patched before `props`, which is necessary for `<select value>`, but the opposite is true for `<select multiple>`. In vue2, we take that as a special case https://github.com/vuejs/vue/blob/dev/src/platforms/web/runtime/node-ops.js#L7-L13, and this PR(https://github.com/vuejs/vue-next/pull/3202) respe... | 2021-02-10T05:56:42 | 2021-02-10T05:56:42 | {
"+1": 1
} | MEMBER |
vuejs | core | 776,539,932 | 3,100 | HcySunYang | Read this for more details https://github.com/vuejs/vue-next/pull/3106#issuecomment-768150000 | 2021-02-10T08:40:29 | 2021-02-10T08:40:29 | {} | MEMBER |
vuejs | core | 776,884,508 | 3,219 | pikax | > 👍 simpler than I expected, ty. Should I open a new issue for the TSX problem, this doesn't fix it.
TSX is not related with this, can you create another issue for the TSX problem? | 2021-02-10T17:34:19 | 2021-02-10T17:34:19 | {} | MEMBER |
vuejs | core | 777,225,906 | 3,223 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.56 KB (0%) |
| runtime-dom.global.prod.js | 26.95 KB (0%) |
| size-check.global.prod.js | 16.33 KB (0%) | | 2021-02-11T06:16:12 | 2021-02-11T06:16:12 | {} | NONE |
vuejs | core | 777,314,416 | 2,613 | Mister-Hope | Do you have any workarounds better than `(Teleport as unknown) as string`? @LeBenLeBen | 2021-02-11T09:38:03 | 2021-02-11T09:38:03 | {} | NONE |
vuejs | core | 778,037,300 | 2,979 | HcySunYang | Due to https://github.com/vuejs/vue-next/commit/03360cefa1b7038174fa3c1fc3a04400b4cdbbce | 2021-02-12T07:50:03 | 2021-02-12T07:50:03 | {} | MEMBER |
vuejs | core | 778,445,647 | 3,228 | LinusBorg | https://github.com/vuejs/rfcs/blob/script-setup-2/active-rfcs/0000-script-setup.md#closed-by-default | 2021-02-12T20:46:25 | 2021-02-12T20:46:25 | {} | MEMBER |
vuejs | core | 778,907,380 | 3,080 | HcySunYang | > I imagine it's pretty hard to write a proper test for this, but can you think of a way to test this?
Would like to ship this with the next patch.
yeah, let me try | 2021-02-15T02:59:23 | 2021-02-15T02:59:23 | {} | MEMBER |
vuejs | core | 774,741,164 | 2,834 | LinusBorg | There's ongoing discussion about another way to solve this here: #3184
We should resolve that discussion before deciding wether to merge this PR or the other one. | 2021-02-07T19:18:19 | 2021-02-07T19:18:19 | {} | MEMBER |
vuejs | core | 774,912,666 | 3,195 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.56 KB (0%) |
| runtime-dom.global.prod.js | 26.95 KB (0%) |
| size-check.global.prod.js | 16.32 KB (0%) | | 2021-02-08T06:44:30 | 2021-02-08T06:44:30 | {} | NONE |
vuejs | core | 774,938,604 | 2,975 | yangmingshan | I agree, I'm closing this, and open #3196 | 2021-02-08T07:35:50 | 2021-02-08T07:35:50 | {} | CONTRIBUTOR |
vuejs | core | 775,702,691 | 2,064 | kris-ellery | @tomhrtly I stopped looking once I got it working with Vite. | 2021-02-09T06:25:05 | 2021-02-09T06:25:05 | {} | NONE |
vuejs | core | 775,907,051 | 3,207 | Obdormio | if we add v-if or v-show or some children to the div, it will work properly.
sample:
```
<transition name="empty">
<div>Some content</div>
</transition>
<transition name="empty">
<div v-if="visible"></div>
</transition>
``` | 2021-02-09T12:38:26 | 2021-02-09T12:38:26 | {} | NONE |
vuejs | core | 778,589,118 | 384 | LinusBorg | Even though an old PR, this still seems like a good addition.
Before getting back to this and solving merge conflicts though, we should fix some of the existing bugs first (see `teleport` labels) | 2021-02-13T09:21:46 | 2021-02-13T09:21:46 | {} | MEMBER |
vuejs | core | 778,616,849 | 3,229 | HcySunYang | Why do you think this is not up to expectations? Obviously, you need to use `v-model`. | 2021-02-13T13:07:49 | 2021-02-13T13:07:49 | {} | MEMBER |
vuejs | core | 775,913,657 | 1,539 | mpblewitt | The `-s` that is being appended in [comment](https://github.com/vuejs/vue-next/blob/58b07069ad33c8a8e44cb47b81084a452dda2846/packages/runtime-core/src/renderer.ts#L727-L731https://duckduckgo.com/?t=ffab&q=this+is+a+slot+content+node&atb=v197-1&ia=webl) is also breaking Scoped CSS on slot content which was fixed to addr... | 2021-02-09T12:51:33 | 2021-02-09T12:51:33 | {
"+1": 1
} | NONE |
vuejs | core | 778,450,423 | 3,227 | LinusBorg | The current implementation allows to receive an array of callbacks in the transition's prop definition, but calls it like a function, without checking for an array:
I assume `onLeave` should be called with `callHook` like the other hooks, but right now I'm not sure if there's any side effect with `callHook`'s async ... | 2021-02-12T20:56:24 | 2021-02-12T20:56:53 | {} | MEMBER |
vuejs | core | 778,916,065 | 3,070 | oliverzy | How is this feature related to "Suspense + Async Setup"? | 2021-02-15T03:35:05 | 2021-02-15T03:35:05 | {} | NONE |
vuejs | core | 778,931,413 | 2,764 | edison1105 | > This make #2583 happen again.
I dont think so,I tested it and it works fine. | 2021-02-15T04:36:28 | 2021-02-15T04:52:40 | {} | MEMBER |
vuejs | core | 774,684,694 | 3,039 | HcySunYang | Can this be achieved through LibraryManagedAttributes and Template Literal Types? Instead of enumerating? Like this one https://github.com/vuejs/vue-next/pull/3096 | 2021-02-07T14:38:31 | 2021-02-07T14:38:31 | {} | MEMBER |
vuejs | core | 774,809,280 | 3,153 | huxianc | > I close this one because it cannot be reproduced and is not active. If there is still a problem, you can open another issue
Thaks! I opened an new issue #3189 , and uploaded screenshot in both mode (dev and production) | 2021-02-08T01:19:16 | 2021-02-08T01:19:16 | {} | NONE |
vuejs | core | 774,912,119 | 3,194 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.56 KB (0%) |
| runtime-dom.global.prod.js | 26.95 KB (0%) |
| size-check.global.prod.js | 16.32 KB (0%) | | 2021-02-08T06:43:26 | 2021-02-08T06:43:26 | {} | NONE |
vuejs | core | 775,913,967 | 3,207 | HcySunYang | Has been fixed in https://github.com/vuejs/vue-next/commit/347a8798a4c5f0b426f3ac84a01d752d823fb51b | 2021-02-09T12:52:10 | 2021-02-09T12:52:10 | {
"rocket": 1
} | MEMBER |
vuejs | core | 777,312,992 | 2,614 | Mister-Hope | Any plan to have this merged? @LinusBorg Just a single line change. | 2021-02-11T09:35:32 | 2021-02-11T09:39:12 | {} | NONE |
vuejs | core | 775,914,648 | 3,207 | HcySunYang | Not yet released | 2021-02-09T12:53:22 | 2021-02-09T12:53:22 | {} | MEMBER |
vuejs | core | 776,479,336 | 3,188 | HcySunYang | When using the template ref on async component:
```html
<AsyncComp ref="myRef" />
```
This `ref` will be forwarded to the inner component, ideally, the inner component should take over the ref completely, but it will be set to `null` every time an async component is patched, see the [setRef](https://github.com/... | 2021-02-10T06:30:50 | 2021-02-10T06:30:50 | {} | MEMBER |
vuejs | core | 776,590,255 | 3,072 | HcySunYang | The hoisted DOM may be reused, since only static DOM nodes will be hoisted, therefor we use `cloneNode` to generate clones of it in the production env, but this will not copy custom DOM props.
In the `patchDOMProp`, we store the actual value of DOM in the `_value` property, so we need to keep it when doing clones.
| 2021-02-10T09:56:30 | 2021-02-10T09:56:30 | {} | MEMBER |
vuejs | core | 778,037,122 | 2,972 | HcySunYang | Can be fixed in https://github.com/vuejs/vue-next/commit/03360cefa1b7038174fa3c1fc3a04400b4cdbbce | 2021-02-12T07:49:30 | 2021-02-12T07:49:30 | {} | MEMBER |
vuejs | core | 778,594,724 | 3,157 | HcySunYang | @LinusBorg This PR did not solve #2870, I think we can merge #2870 first, and then I will deal with the conflict. | 2021-02-13T10:13:21 | 2021-02-13T10:13:21 | {
"+1": 1
} | MEMBER |
vuejs | core | 778,649,315 | 3,080 | LinusBorg | I imagine it's pretty hard to write a proper test for this, but can you think of a way to test this?
Would like to ship this with the next patch. | 2021-02-13T17:26:28 | 2021-02-13T17:26:50 | {} | MEMBER |
vuejs | core | 881,262,943 | 3,870 | AurelieV | We are facing the same problem: migration from vue2 to vue3, we were using prerender strategy instead of SSR. Our code is currently not ready without a lot of effort for SSR, and with vue3 migration, hydration from a prerender is impossible
- if you use createApp, mount does not take into account the second param, and... | 2021-07-16T08:12:23 | 2021-07-16T08:12:23 | {} | NONE |
vuejs | core | 882,699,873 | 4,148 | posva | Closing in favor of https://github.com/vuejs/vue-next/issues/4149 | 2021-07-19T16:48:34 | 2021-07-19T16:48:34 | {} | MEMBER |
vuejs | core | 882,734,271 | 4,148 | yyx990803 | FYI this is not entirely the same as #4149 as it also involves a scheduler bug where computed scheduler jobs are not correctly appended (fixed in d810a1a5) | 2021-07-19T17:39:34 | 2021-07-19T17:39:34 | {
"eyes": 1
} | MEMBER |
vuejs | core | 882,860,572 | 4,144 | yyx990803 | Hmm, I don't think this is necessary, but thanks for the PR. | 2021-07-19T21:08:22 | 2021-07-19T21:08:22 | {} | MEMBER |
vuejs | core | 882,875,702 | 3,575 | yyx990803 | Saw this too late 😂
I landed the same in https://github.com/vuejs/vue-next/commit/1ffd48a2f5fd3eead3ea29dae668b7ed1c6f6130 and 93a950d6 | 2021-07-19T21:32:18 | 2021-07-19T21:32:18 | {} | MEMBER |
vuejs | core | 880,997,114 | 2,109 | yyx990803 | This is stale and should no longer be necessary. | 2021-07-15T20:37:42 | 2021-07-15T20:37:42 | {} | MEMBER |
vuejs | core | 881,135,764 | 4,104 | mzaini30 | > fixed by [c0db807](https://github.com/vuejs/vue-next/commit/c0db807844194a227f6d0dad6cc3e1e8f148770f)
Can I use that commit now? I have same problem. | 2021-07-16T02:44:51 | 2021-07-16T02:44:51 | {} | NONE |
vuejs | core | 881,258,684 | 4,127 | bingtimren | My understanding is that inside "setup", the component instance is not available, as it's not created yet. However for things setup by the composition API, the aim is to be feature-complete compared to options API. As quote from [here](https://v3.vuejs.org/guide/composition-api-introduction.html#lifecycle-hook-registra... | 2021-07-16T08:05:33 | 2021-07-16T08:05:33 | {} | NONE |
vuejs | core | 881,845,366 | 4,138 | syuilo | Probably the reason for this is that the handling of the case where the style is a string is missing [here](https://github.com/vuejs/vue-next/blob/327c8983fb9b04c7f819cd0c5a2b3d4ff69c7822/packages/shared/src/normalizeProp.ts#L6).
Or maybe don't even need to generate the code to call normalizeStyle at the compilation... | 2021-07-17T06:58:27 | 2021-07-17T07:00:53 | {} | CONTRIBUTOR |
vuejs | core | 881,859,788 | 4,140 | edison1105 | your reproduction link is broken. | 2021-07-17T08:50:48 | 2021-07-17T08:50:48 | {} | MEMBER |
vuejs | core | 882,594,959 | 4,130 | webfansplz | > AFAIK `<portal>` isn't formally part of the spec yet.
fix!
| 2021-07-19T14:28:07 | 2021-07-19T14:28:07 | {} | MEMBER |
vuejs | core | 882,903,370 | 4,151 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2021-07-19T22:29:01 | 2021-07-19T22:29:01 | {} | CONTRIBUTOR |
vuejs | core | 882,362,969 | 4,145 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2021-07-19T08:41:48 | 2021-07-19T08:41:48 | {} | CONTRIBUTOR |
vuejs | core | 882,641,788 | 4,144 | yyx990803 | If a timeout callback has already triggered, calling `clearTimeout` on that handle will simply be a noop. So clearing the handle when the callback is triggered doesn't actually affect the behavior in anyway... or am I missing something? | 2021-07-19T15:27:33 | 2021-07-19T15:27:33 | {} | MEMBER |
vuejs | core | 882,882,869 | 3,957 | yyx990803 | See 3056e9b3 - only need to check vnode props for the type.
I used the test from this PR though - thanks! | 2021-07-19T21:46:34 | 2021-07-19T21:46:34 | {} | MEMBER |
vuejs | core | 883,167,210 | 3,814 | posva | Thanks for the PR, apparently this got fixed at https://github.com/vuejs/vue-next/commit/3056e9b3dcb1ab0bd18227c6fa7bf283f98f6ef6 | 2021-07-20T07:35:31 | 2021-07-20T07:35:31 | {} | MEMBER |
vuejs | core | 883,388,963 | 4,148 | AlexandreBonaventure | FYI, I upgraded to 3.2.0-beta-2 and while the repro is now working, our repo that initiated this issue is still failing. Will update soon | 2021-07-20T13:22:52 | 2021-07-20T13:22:52 | {} | CONTRIBUTOR |
vuejs | core | 883,553,103 | 4,157 | posva | Also reproducible with a much simpler version similar to https://github.com/vuejs/vue-next/issues/4148#issuecomment-882697559
```ts
import { h } from 'vue';
import { createRouter, createWebHistory, RouteRecordRaw, RouterView } from 'vue-router';
const routes: RouteRecordRaw[] = [
{
path: '/',
compo... | 2021-07-20T17:06:09 | 2021-07-20T17:06:09 | {} | MEMBER |
vuejs | core | 881,061,993 | 3,943 | yyx990803 | The root cause:
- `Foo` is placed at root of `Bar`
- When Foo is mounted, the renderer did not properly enter "optimized" mode because the check only happens when patching children.
- The first update triggers inside Foo, which performs an optimized update;
- The 2nd update is from the outside, which causes Foo's... | 2021-07-15T22:58:34 | 2021-07-15T22:58:34 | {} | MEMBER |
vuejs | core | 881,302,701 | 4,126 | posva | This is expected because the whole template re renders.
---
Please, next time consider using the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js) for questions first. But feel free to come back and open an issue if it turns o... | 2021-07-16T09:17:47 | 2021-07-16T09:17:47 | {} | MEMBER |
vuejs | core | 881,494,125 | 4,129 | yyx990803 | Yeah it seems we need to lazy define the `VueElement` class for SSR env. But I'm curious why the cjs build of `@vue/runtime-dom` is loaded here... | 2021-07-16T14:31:22 | 2021-07-16T14:31:22 | {} | MEMBER |
vuejs | core | 882,725,309 | 4,142 | leno23 | thanks for merge! ^.^ | 2021-07-19T17:24:50 | 2021-07-19T17:24:50 | {} | CONTRIBUTOR |
vuejs | core | 882,955,415 | 3,957 | edison1105 | @yyx990803
oh no, you should close https://github.com/vuejs/vue-next/pull/3814, not this one. 😆 | 2021-07-20T00:34:37 | 2021-07-20T00:34:37 | {} | MEMBER |
vuejs | core | 883,394,803 | 4,153 | yyx990803 | Bailing on failed builds is by design - there should not be build errors so if it happens it needs to be fixed. | 2021-07-20T13:30:55 | 2021-07-20T13:30:55 | {} | MEMBER |
vuejs | core | 884,450,069 | 4,165 | yyx990803 | `deferredComputed` is not exposed in Vue so it should not show up in normal Vue applications...
Why are you relying on `effect.computed`? I mean it was in the beta and removed during beta so technically it never was part of the stable API... | 2021-07-21T19:44:38 | 2021-07-21T19:44:38 | {} | MEMBER |
vuejs | core | 884,454,285 | 4,165 | posva | > Why are you relying on effect.computed? I mean it was in the beta and removed during beta so technically it never was part of the stable API...
Ah 🤣 I used it for Pinia to extract and differentiate state property from getters for devtools and also because state is moved to a global state object (`pinia.state.valu... | 2021-07-21T19:51:15 | 2021-07-21T19:51:15 | {} | MEMBER |
vuejs | core | 880,977,848 | 4,119 | jacekkarczmarczyk | > provide key **should not be number** type
> No, you **should not be using numbers** as provide keys.
wat | 2021-07-15T20:04:39 | 2021-07-15T20:04:39 | {} | CONTRIBUTOR |
vuejs | core | 881,293,814 | 4,127 | LinusBorg | If you need access to `this`, use the normal Options API lifecycle hook.
The goal of composition API is to be more explicit and remove indirection. By removing access to `this`, which could have any arbitrary properties from mixins, global properties and so on, composition lifecycle hooks need explicit references i... | 2021-07-16T09:03:44 | 2021-07-16T09:03:44 | {} | MEMBER |
vuejs | core | 881,869,930 | 4,140 | xGuangsPBD | > I think it's not a bug. see https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2IHYtZm9yPVwiKHJvdyx5KSBpbiBsaXN0XCIgOmtleT1cInlcIj5cbiAgICA8ZGl2PlxuICAgICAgLS0tIHJvdyB7e3l9fVxuICAgIDwvZGl2PlxuICAgIDxkaXYgdi1mb3I9XCIobnVtLHgpIGluIHJvd1wiIEBjbGljaz1cImhhbmRsZUNsaWNrKHgseSlcIj5cbiAgICAgIHt7bnVtfX1cbiAgICA8L2R... | 2021-07-17T09:53:31 | 2021-07-17T09:53:31 | {} | NONE |
vuejs | core | 882,863,043 | 4,091 | yyx990803 | The reason it is using `!` here is because by the logic of `BaseTranstion`, only mounted vnodes could ever be saved in the leavingVNodes cache. So if vnodes in the cache has `null` el values, there's something wrong elsewhere. (Which is why we want a reproduction so we can fix the actual root cause) | 2021-07-19T21:11:58 | 2021-07-19T21:11:58 | {} | MEMBER |
vuejs | core | 882,875,946 | 3,571 | yyx990803 | Supported via 1ffd48a + 93a950d6 | 2021-07-19T21:32:46 | 2021-07-19T21:32:46 | {} | MEMBER |
vuejs | core | 883,668,918 | 4,159 | yyx990803 | This is expected behavior because the comments are necessary for correct client-side hydration (because of potential async components inside fragments) | 2021-07-20T20:20:29 | 2021-07-20T20:20:29 | {} | MEMBER |
vuejs | core | 884,453,065 | 4,167 | yyx990803 | `isString` and similar helpers are primarily used in runtime code to reduce bundle size. Many of the cases here are in non-runtime packages (compiler or Node-only packages) so it doesn't matter.
`isObject` is also avoided where we already excluded `null` values first. | 2021-07-21T19:49:25 | 2021-07-21T19:49:25 | {} | MEMBER |
vuejs | core | 881,163,580 | 3,949 | Trinovantes | I finally figured out why I was getting hydration errors only in production. My build script was `NODE_ENV=production webpack --config webpack.config.client.ts && webpack --config build/webpack.config.server.ts` but I forgot shell only exports the `NODE_ENV` variable to the first command.
As a result, I was compilin... | 2021-07-16T04:16:40 | 2021-07-16T04:16:40 | {} | NONE |
vuejs | core | 881,200,782 | 4,127 | LinusBorg | you generally can't access the component instance through `this` anywhere in composition API. It's one of its design principles, basically.
If you want to propose improvements to the docs, the docs team over at the vuejs/doc-next repo is happy for some suggestions or a PR. | 2021-07-16T06:05:15 | 2021-07-16T06:05:15 | {} | MEMBER |
vuejs | core | 881,300,494 | 4,128 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js). | 2021-07-16T09:14:31 | 2021-07-16T09:14:31 | {} | MEMBER |
vuejs | core | 882,094,912 | 4,010 | LinusBorg | You can actually sort the elements yourself, may be a viable workaround for the time being:
```js
onUpdated(() => {
console.log(sortElementsByPosition(itemRefs));
});
function sortElementsByPosition(elements) {
return elements.slice().sort((a, b) => {
return a.compareDocumentP... | 2021-07-18T17:55:45 | 2021-07-18T17:56:23 | {
"confused": 1,
"eyes": 2
} | MEMBER |
vuejs | core | 882,595,870 | 4,144 | yyx990803 | This doesn't seem to change anything. | 2021-07-19T14:29:16 | 2021-07-19T14:29:16 | {} | MEMBER |
vuejs | core | 880,975,088 | 4,119 | yyx990803 | No, you should not be using numbers as provide keys. | 2021-07-15T20:00:01 | 2021-07-15T20:00:01 | {} | MEMBER |
vuejs | core | 881,838,731 | 4,136 | leopsidom | Hmm, I think you are correct. @lidlanca I must have missed something else in my code :( | 2021-07-17T06:14:05 | 2021-07-17T06:14:05 | {} | NONE |
vuejs | core | 882,299,771 | 4,143 | LinusBorg | ```html
<div class="app">
<div id="topbar"></div>
<main>
<teleport :disabled="!mobile" to="#topbar">
<div class="fixed w-full">
... exact same large portion of template
</div>
</teleport>
</main>
</div>
```
https://v3.vuejs.org/api/built-in-components.html#te... | 2021-07-19T07:09:57 | 2021-07-19T07:09:57 | {} | MEMBER |
vuejs | core | 882,627,929 | 4,147 | yyx990803 | Note: this alone does not fix #4146 | 2021-07-19T15:09:45 | 2021-07-19T15:09:45 | {} | MEMBER |
vuejs | core | 882,697,559 | 4,148 | posva | Trying to boil it down without Vue Router by simulating the injected `$route` but still haven't found it.
A much simpler repro is without nested routes, nor redirects:
```ts
import { h } from '@vue/runtime-core'
import { createRouter, createWebHistory, RouteRecordRaw } from 'vue-router'
const routes: RouteRe... | 2021-07-19T16:44:54 | 2021-07-19T16:44:54 | {} | MEMBER |
vuejs | core | 882,767,618 | 4,010 | DV8FromTheWorld | Interesting. Didn't know about [Node.compareDocumentPosition](https://developer.mozilla.org/en-US/docs/Web/API/Node/compareDocumentPosition). | 2021-07-19T18:32:01 | 2021-07-19T18:32:01 | {} | CONTRIBUTOR |
vuejs | core | 882,877,287 | 3,538 | yyx990803 | In general we do not accept code-style only PRs, as most style is subjective and code should be optimized for the reading habits of maintainers who work with it daily. I don't think this change is necessary. It also conflicts with the style in other files. | 2021-07-19T21:35:11 | 2021-07-19T21:35:11 | {} | MEMBER |
vuejs | core | 883,779,756 | 4,161 | andrewcourtice | This may be related to #4155 | 2021-07-20T23:55:52 | 2021-07-20T23:55:52 | {} | NONE |
vuejs | core | 881,069,325 | 2,016 | CyberAP | I am strongly relying on hydration detection and forced rehydration mechanism up to this day in Vue 2. The implementation doesn't really matter that much to me, its more important that I can have a reliable way to detect a hydration in Vue 3. Looking forward for Vue 3.3! | 2021-07-15T23:18:42 | 2021-07-15T23:18:42 | {} | CONTRIBUTOR |
vuejs | core | 881,164,320 | 4,126 | dengpeida | However, if the countdown content is placed in the Button component of Ant-Design-Vue, this problem will not occur | 2021-07-16T04:19:10 | 2021-07-16T04:19:10 | {} | NONE |
vuejs | core | 881,472,366 | 2,164 | yyx990803 | @pikax mind rebasing on latest 3.2 branch? | 2021-07-16T14:00:26 | 2021-07-16T14:00:26 | {} | MEMBER |
vuejs | core | 881,522,175 | 4,010 | DV8FromTheWorld | I would expect that the ordering of refs received would be stable between renders (and between Vue2 and Vue3).
Without it being stable it makes things like "focus the first ref in the list" quite difficult as the ordering will reverse after the initial render.
Here is a simplified repro example that shows that re-r... | 2021-07-16T15:12:36 | 2021-07-16T15:12:36 | {} | CONTRIBUTOR |
vuejs | core | 881,696,960 | 3,921 | yyx990803 | Fixed in `vue-loader@16.3.1`. | 2021-07-16T20:21:59 | 2021-07-16T20:21:59 | {} | MEMBER |
vuejs | core | 882,626,346 | 4,139 | syuilo | IMO, To avoid the overhead of function calls, it should be possible to skip them, at least if the string is set directly, since it is known at the compilation stage. | 2021-07-19T15:07:58 | 2021-07-19T15:07:58 | {} | CONTRIBUTOR |
vuejs | core | 884,443,062 | 4,164 | yyx990803 | <img width="650" alt="Screen Shot 2021-07-21 at 3 33 00 PM" src="https://user-images.githubusercontent.com/499550/126548824-3ff037a2-bea2-4706-9325-48e329f7f4c6.png">
There already is a compiler error for this. | 2021-07-21T19:33:15 | 2021-07-21T19:33:15 | {} | MEMBER |
vuejs | core | 881,158,438 | 4,104 | edison1105 | > > fixed by [c0db807](https://github.com/vuejs/vue-next/commit/c0db807844194a227f6d0dad6cc3e1e8f148770f)
>
>
>
> Can I use that commit now? I have same problem.
not release yet | 2021-07-16T04:00:03 | 2021-07-16T04:00:03 | {
"eyes": 1
} | MEMBER |
vuejs | core | 881,571,183 | 4,010 | DV8FromTheWorld | This is actually pretty problematic for us in terms of migrating to Vue3. We have lots of accessibility functionalities that rely on being able to properly traverse our `$refs` for keyboard navigation, focus transferring, etc.
Without a stable, in-order sort for these refs.. we're kinda stuck. | 2021-07-16T16:28:25 | 2021-07-16T16:28:25 | {} | CONTRIBUTOR |
vuejs | core | 882,865,983 | 3,909 | yyx990803 | Please don't make PRs just for the sake of making PRs. These changes do not affect behavior or code quality and only wastes maintainers' time to review and explain why it should not be accepted. | 2021-07-19T21:16:51 | 2021-07-19T21:16:51 | {} | MEMBER |
vuejs | core | 880,995,420 | 2,984 | yyx990803 | #2983 closed via afdd2f2 | 2021-07-15T20:34:41 | 2021-07-15T20:34:41 | {} | MEMBER |
vuejs | core | 881,062,037 | 3,945 | yyx990803 | See https://github.com/vuejs/vue-next/issues/3943#issuecomment-881061993 | 2021-07-15T22:58:41 | 2021-07-15T22:58:41 | {} | MEMBER |
vuejs | core | 881,280,197 | 4,127 | jacekkarczmarczyk | I wouldn't consider "having access to `this`" as a feature, it's only an API. The feature would be "having access to the component instance" which is a thing in Composition API, just the way you use this feature is different in Composition API and Options API | 2021-07-16T08:41:05 | 2021-07-16T08:41:05 | {} | CONTRIBUTOR |
vuejs | core | 881,309,819 | 4,127 | bingtimren | Thanks. Now I understand more about the design considerations of the composition API.
One last comment - the methods registered with composition API do have access to "this". Maybe they should be kept the same as everyone else - watches, lifecycle callbacks, etc. | 2021-07-16T09:28:55 | 2021-07-16T09:28:55 | {} | NONE |
vuejs | core | 881,573,907 | 3,922 | yyx990803 | See 6ed23f6 - the bug affects more than just `<transition>`: it occurs when:
- a child component is used at root level
- the child component contains slot content that may change
- the slot content change depends on state that isn't used by the parent (so parent `onUpdated` doesn't trigger when the child updates)
... | 2021-07-16T16:33:13 | 2021-07-16T16:33:13 | {
"+1": 1
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.