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 | 717,897,018 | 2,507 | edison1105 | > ok. And how I can access the global properties inside the setup()?
see https://github.com/vuejs/vue-next/issues/2233 | 2020-10-28T12:21:40 | 2020-10-28T12:21:40 | {} | MEMBER |
vuejs | core | 715,301,768 | 2,472 | unbyte | was #2457 caused by the same reason? | 2020-10-23T12:07:34 | 2020-10-23T12:07:34 | {} | CONTRIBUTOR |
vuejs | core | 716,028,866 | 2,479 | 07akioni | vue2 会把你原对象做改动，vue3 不会，所以你加入一个非响应式的对象变化不会被追踪 | 2020-10-24T17:36:25 | 2020-10-24T17:36:25 | {} | CONTRIBUTOR |
vuejs | core | 716,056,787 | 2,480 | Maronato | https://github.com/vuejs/vue-next/issues/2429 already reported this, my bad | 2020-10-24T21:21:10 | 2020-10-24T21:21:10 | {} | NONE |
vuejs | core | 716,427,034 | 2,487 | posva | Feel free to open a PR with a benchmark to prove the improvement! | 2020-10-26T09:32:42 | 2020-10-26T09:32:42 | {} | MEMBER |
vuejs | core | 717,170,545 | 2,496 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-27T11:14:03 | 2020-10-27T11:14:03 | {} | NONE |
vuejs | core | 717,821,162 | 2,504 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-28T09:51:00 | 2020-10-28T09:51:00 | {} | NONE |
vuejs | core | 717,982,984 | 2,509 | LinusBorg | This still doesn't have a runnable reproduction, nor does it have a meaningful description. I have no idea what the problem is supposed to be. You don't show how you actually use that component.
Provide a runnable reproduction and I can re-open this. | 2020-10-28T14:47:02 | 2020-10-28T14:47:02 | {} | MEMBER |
vuejs | core | 716,025,037 | 2,479 | unbyte | 我的意思是你的用法不对，像我这样写 | 2020-10-24T17:28:15 | 2020-10-24T17:28:15 | {} | CONTRIBUTOR |
vuejs | core | 716,192,020 | 2,484 | anish2690 | behaviour is same after sharing vue as singleton
```js
shared: {
vue: {
singleton: true,
},
'@vue/compiler-sfc': {
singleton: true,
},
'vue-loader': {
singleton: true,
},
} | 2020-10-25T18:40:02 | 2020-10-25T18:40:32 | {} | NONE |
vuejs | core | 716,253,418 | 2,484 | ScriptedAlchemy | You can just share @vue/
And it'll share all the subsets.
Don't share loaders. Also use required version | 2020-10-26T01:27:42 | 2020-10-26T01:27:42 | {
"+1": 1
} | NONE |
vuejs | core | 717,013,938 | 2,448 | AaronBank | Ok thanks for reply | 2020-10-27T06:22:14 | 2020-10-27T06:22:14 | {} | NONE |
vuejs | core | 717,820,500 | 2,501 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-28T09:49:51 | 2020-10-28T09:49:51 | {} | NONE |
vuejs | core | 717,820,679 | 2,502 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-28T09:50:09 | 2020-10-28T09:50:09 | {} | NONE |
vuejs | core | 717,824,681 | 2,493 | lixiaofa | and readonlyState.includes ("a") to be collected dependency, readonlystate [0] will not be collected dependency ， Any thoughts | 2020-10-28T09:57:34 | 2020-10-28T10:34:35 | {} | NONE |
vuejs | core | 717,854,874 | 2,506 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 40.15 KB (-0.01% 🔽) |
| runtime-dom.global.prod.js | 26.43 KB (-0.01% 🔽) |
| size-check.global.prod.js | 15.95 KB (-0.01% 🔽) | | 2020-10-28T10:55:35 | 2020-10-28T10:55:35 | {} | NONE |
vuejs | core | 718,246,844 | 2,116 | CyberAP | @LinusBorg but how are end users are going to benefit from the unified behaviour for both objects and arrays? I couldn't think of a case where we explicitly don't want to watch for array mutations, but I certainly can imagine cases where we don't want to watch for object mutations. Objects and arrays are used different... | 2020-10-28T22:33:37 | 2020-10-28T22:33:37 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 715,558,265 | 2,475 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-23T19:51:29 | 2020-10-24T16:23:25 | {} | NONE |
vuejs | core | 716,026,960 | 2,479 | Tzdy | 好吧，懂了 | 2020-10-24T17:30:17 | 2020-10-24T17:30:17 | {} | NONE |
vuejs | core | 716,508,690 | 2,488 | zigomir | @posva I see. Actually very similar issue happens with `$emit()` – please see this [sandbox](https://codesandbox.io/s/vue-3-emit-event-names-ouovq?file=/src/App.vue) & open console. I suspect it will be fixed in same PR so I didn't open new issue. | 2020-10-26T12:15:17 | 2020-10-26T12:15:17 | {} | NONE |
vuejs | core | 716,750,575 | 2,488 | zigomir | For posterity: `$emit` is fixed when you use latest `@vue/compiler-sfc` as described in https://github.com/vuejs/vue-next/issues/2429 | 2020-10-26T18:45:26 | 2020-10-26T18:45:26 | {} | NONE |
vuejs | core | 717,633,105 | 2,497 | edison1105 | We can also do this in `Vetur` | 2020-10-28T01:11:13 | 2020-10-28T01:11:13 | {} | MEMBER |
vuejs | core | 717,822,631 | 2,493 | lixiaofa | I'd like to ask why this design is so designed
readonly(["a", "b", "c"])
I mean, why don't you collect dependencies in both cases, or not | 2020-10-28T09:53:51 | 2020-10-28T10:34:45 | {} | NONE |
vuejs | core | 717,118,849 | 2,493 | LinusBorg | You misunderstand what `readonly` does. This is expected behaviour. readonly still allows for values to be collected as dependencies - it only keep you from mutating the source objects through the procxy returned by `readonly`.
Maybe you are looking for `markRaw()` or one of the `shallow*()` APIs.
Edit: my anal... | 2020-10-27T09:47:08 | 2020-10-28T10:35:26 | {} | MEMBER |
vuejs | core | 718,087,538 | 2,511 | yyx990803 | This is expected behavior. `setup()` is not part of the options API and is excluded from any form of options-based composition/inheritance.
If you use `setup()`, composition should happen via Composition API. | 2020-10-28T17:22:39 | 2020-10-28T17:22:39 | {
"+1": 2
} | MEMBER |
vuejs | core | 718,164,957 | 2,503 | dependabot-preview[bot] | Superseded by #2512. | 2020-10-28T19:39:26 | 2020-10-28T19:39:26 | {} | CONTRIBUTOR |
vuejs | core | 715,900,362 | 2,381 | LinusBorg | Managed to reproduce it:
https://jsfiddle.net/Linusborg/4w8gjvph/6/
Still looking into the specifics of what happens and wether tim-janik's proposed fix is the right one, but as he explained, it's related to a mismatch of `currentInstance` and `instance`, the 4th argument of `doWatch`
As `this.$watch` is the o... | 2020-10-24T11:17:19 | 2020-10-24T12:34:33 | {} | MEMBER |
vuejs | core | 717,819,943 | 2,499 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-28T09:48:44 | 2020-10-28T09:48:44 | {} | NONE |
vuejs | core | 717,837,055 | 2,493 | lixiaofa | OK, thank you | 2020-10-28T10:20:33 | 2020-10-28T10:20:33 | {} | NONE |
vuejs | core | 717,934,616 | 2,507 | mpricu | Thank you very much, now it works. The documentation for global properties still need to be updated. | 2020-10-28T13:31:44 | 2020-10-28T13:31:44 | {} | NONE |
vuejs | core | 718,009,781 | 1,409 | znck | Can't you use top level import and depend on tree shaking in end application? | 2020-10-28T15:25:49 | 2020-10-28T15:25:49 | {} | MEMBER |
vuejs | core | 715,300,118 | 2,471 | posva | That's not a valid reproduction.
Looks similar to https://github.com/vuejs/vue-next/issues/2429 | 2020-10-23T12:03:42 | 2020-10-23T12:03:42 | {} | MEMBER |
vuejs | core | 715,324,772 | 2,471 | ulf1 | Updating @vue/compiler-sfc was the solution
https://github.com/vuejs/vue-next/issues/2429#issuecomment-713463119 | 2020-10-23T12:58:14 | 2020-10-23T12:58:14 | {} | NONE |
vuejs | core | 715,403,385 | 2,473 | posva | Please open the issue on the relevant repository like vue-class-component if this was already fixed in https://github.com/vuejs/vue-cli/issues/5974 | 2020-10-23T15:12:48 | 2020-10-23T15:12:48 | {} | MEMBER |
vuejs | core | 716,681,291 | 2,489 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [size](https://github.com/vuejs/vue-next/runs/1310112541)
Dependabot will still automatically merge this pull request if you amend it and your tests pass. | 2020-10-26T16:51:27 | 2020-10-26T16:51:27 | {} | CONTRIBUTOR |
vuejs | core | 717,107,520 | 2,483 | pikax | Can you add a test case for that? | 2020-10-27T09:27:43 | 2020-10-27T09:27:43 | {} | MEMBER |
vuejs | core | 717,327,767 | 1,409 | somodevo | I got a similar use case where I need to fetch some data from an API endpoint when/for initialising our SPA. That data needs to be passed to all children. I also need to do `provide(DefaultApolloClient, apolloClient)` some time afterwards in the async function. Anyone have an idea or workaround on how to achieve that? ... | 2020-10-27T15:34:48 | 2020-10-27T15:34:48 | {} | NONE |
vuejs | core | 717,836,016 | 2,493 | lixiaofa | You may have misunderstood the meaning
In the case of readonly(),
Why? readonlyState.includes ("a") to collect dependencies, readonlystate [0] will not collect d... | 2020-10-28T10:18:34 | 2020-10-28T10:18:34 | {} | NONE |
vuejs | core | 717,889,823 | 2,507 | edison1105 | `this `is not available inside `setup()` | 2020-10-28T12:07:02 | 2020-10-28T12:10:17 | {} | MEMBER |
vuejs | core | 753,787,594 | 2,934 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2021-01-04T06:37:02 | 2021-01-04T06:37:02 | {} | NONE |
vuejs | core | 753,911,171 | 2,928 | posva | Closing in favor of https://github.com/vuejs/vue-next/pull/2929 since it affects only initial mounting | 2021-01-04T11:05:16 | 2021-01-04T11:05:16 | {} | MEMBER |
vuejs | core | 754,725,412 | 2,944 | longlho | I mean they have the same root cause :) and also IF there's a escape sequence it'd be nice to have double escaping as well. | 2021-01-05T15:57:58 | 2021-01-05T15:57:58 | {} | NONE |
vuejs | core | 752,769,917 | 2,910 | rhengles | @LinusBorg I understand. The issue is that no application ever would use `Symbol.unscopables` as a key to its own data, this access is coming from the `with(_ctx) {}` that is generated by the template compiler, not from my application, so me as a user shouldn't have to see this warning that I can't do anything about.
... | 2020-12-30T21:52:45 | 2020-12-30T21:52:45 | {} | NONE |
vuejs | core | 753,344,101 | 2,922 | LinusBorg | Thanks for reporting. This indeed seems to be a mistake in the types, and made it's way into the docs from there. | 2021-01-01T16:58:50 | 2021-01-01T16:58:50 | {} | MEMBER |
vuejs | core | 753,716,888 | 2,913 | XingtianLiu | > This is caused by having more than one copy of vue included in the app (from the different /node_modules/ in the federated pojects).
>
> You have to configure your way so that only one copy is included.
>
> Since you provided no reproduction, we can't really be more specific.
I see, thank you. My solution:
... | 2021-01-04T01:47:09 | 2021-01-04T08:27:36 | {
"+1": 3
} | NONE |
vuejs | core | 753,966,213 | 2,936 | skirtles-code | @LinusBorg I'm not sure if this is the same as what you had in mind but there is already a docs PR along similar lines:
https://github.com/vuejs/docs-next/pull/779 | 2021-01-04T13:10:56 | 2021-01-04T13:10:56 | {} | CONTRIBUTOR |
vuejs | core | 753,988,960 | 2,936 | LinusBorg | ah, good :) | 2021-01-04T13:57:21 | 2021-01-04T13:57:21 | {} | MEMBER |
vuejs | core | 752,038,444 | 2,904 | posva | It's true this could be an optimization and the change makes sense | 2020-12-29T11:10:13 | 2020-12-29T11:10:13 | {} | MEMBER |
vuejs | core | 750,764,116 | 2,876 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-24T06:18:54 | 2020-12-30T21:07:33 | {} | NONE |
vuejs | core | 752,833,222 | 2,917 | HcySunYang | I think you can use global mixins as an alternative? | 2020-12-31T03:44:38 | 2020-12-31T03:44:38 | {} | MEMBER |
vuejs | core | 752,902,790 | 2,917 | LinusBorg | Vue components don't have a prototype anymore.
We could kind of replicate the behavior with something like this inserted here:
https://github.com/vuejs/vue-next/blob/a2e65ef85352d6233db0839befbe2eec7bae397c/packages/runtime-core/src/componentPublicInstance.ts#L328-L333
```ts
else if (hasOwnProperty(globalPr... | 2020-12-31T09:31:22 | 2020-12-31T15:43:31 | {} | MEMBER |
vuejs | core | 753,342,495 | 2,924 | skirtles-code | Is this the same as #2601? | 2021-01-01T16:45:07 | 2021-01-01T16:45:07 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 753,744,066 | 2,933 | edison1105 | use `ref` instead of `reactive`
reassigning a proxy will not trigger rerender in VCA. | 2021-01-04T03:58:47 | 2021-01-04T03:59:58 | {} | MEMBER |
vuejs | core | 753,943,626 | 2,927 | posva | can you add a test? | 2021-01-04T12:18:02 | 2021-01-04T12:18:02 | {} | MEMBER |
vuejs | core | 753,944,046 | 2,924 | posva | Closing in favor of the older #2601 | 2021-01-04T12:19:00 | 2021-01-04T12:19:00 | {} | MEMBER |
vuejs | core | 754,703,939 | 2,944 | HcySunYang | Not the same, for example:
```js
console.log('}\}') // '}}'
```
But the following is not:
```js
console.log('} }') // '} }'
``` | 2021-01-05T15:24:11 | 2021-01-05T15:24:11 | {} | MEMBER |
vuejs | core | 752,865,617 | 2,214 | softboy99 | Hi
it seems that problems still exists for reactive array | 2020-12-31T06:46:23 | 2020-12-31T06:46:23 | {} | NONE |
vuejs | core | 752,885,414 | 2,917 | palant | In what way? Define a `created()` method and set a property there? Sounds like a rather wasteful and non-straightforward approach.
Note that personally I’m not looking for a work-around, I solved this in another way already. That’s a capability which was present in Vue 2 however and makes migration harder. | 2020-12-31T08:19:49 | 2020-12-31T08:19:49 | {} | NONE |
vuejs | core | 752,905,803 | 2,851 | LinusBorg | > Aside: I haven't checked but I am pretty sure readonly works slightly differently?
> At least you can wrap a reactive instance into a readonly one and get 2 different objects.
> Not sure what happens if you call readonly on the target directly.
reactive proxies and readonly proxies are tracked in individual Weak... | 2020-12-31T09:46:56 | 2020-12-31T09:46:56 | {} | MEMBER |
vuejs | core | 753,608,275 | 2,928 | amw | It seems there is an alternative PR, but if this was to be accepted I think we'd need a test case. There's a lot of commotion around SVG detection in recent PRs and it'd be a shame if this fix regressed at some point. | 2021-01-03T12:15:28 | 2021-01-03T12:15:28 | {} | NONE |
vuejs | core | 753,775,500 | 2,931 | HcySunYang | First of all, you should not directly manipulate the slot's VNode, your code is fragile, and I don't see any meaningful intentions of your code.
The reason for this issue is that the ref(`show`) in the slot only collects the rendering function of the child component as a dependency, but in the sub-components, becaus... | 2021-01-04T06:02:27 | 2021-01-04T06:02:27 | {} | MEMBER |
vuejs | core | 753,803,895 | 2,931 | LaamGinghong | My intention is to have a container wrap the slot. When slot does not exist, this container does not exist either.
However, the demo you gave cannot achieve the function I want. I don't want to give this control to the outside.😢
> First of all, you should not directly manipulate the slot's VNode, your code is frag... | 2021-01-04T07:19:12 | 2021-01-04T07:19:12 | {} | NONE |
vuejs | core | 755,033,858 | 2,364 | und3fined | @FloppyNotFound i'm make a build production for run in KaiOS
| 2021-01-06T02:22:38 | 2021-01-06T02:22:38 | {} | NONE |
vuejs | core | 752,018,345 | 2,904 | liaoliao666 | > I would say `watchEffect` is different from `watch` which does observe the value: `watchEffect` tracks changes to `d`.
i get ur mean, but why does set the same value will trigger the effect. im still confused | 2020-12-29T09:58:11 | 2020-12-29T09:58:11 | {} | CONTRIBUTOR |
vuejs | core | 752,044,370 | 2,907 | LinusBorg | Good catch, thanks for the report. PR is already up :) | 2020-12-29T11:33:16 | 2020-12-29T11:33:16 | {} | MEMBER |
vuejs | core | 752,252,878 | 2,912 | LinusBorg | Possible, could have missed that. | 2020-12-29T21:48:57 | 2020-12-29T21:48:57 | {} | MEMBER |
vuejs | core | 752,859,283 | 2,860 | HcySunYang | I think the root cause is here(According to [this comment](https://github.com/vuejs/rollup-plugin-vue/issues/401#issuecomment-748301197)):
```js
script.render = render;
script.__scopeId = "data-v-8c4b8c4a";
```
I think we only need to make `render ` and `__scopeId ` as part of the `defineComponent` function pa... | 2020-12-31T06:17:14 | 2020-12-31T06:17:14 | {} | MEMBER |
vuejs | core | 752,989,862 | 2,910 | rhengles | @LinusBorg Thank you for your help!
Of course my fiddle wasn't "intended" to be a way to build production apps, only to show the issue. Now someone else who tries to use the Vue compiler as a step of their workflow can search for this issue and know what they need to do to remove this warning message. ❤
Do you or... | 2020-12-31T15:37:44 | 2020-12-31T15:39:20 | {} | NONE |
vuejs | core | 753,345,102 | 2,925 | LinusBorg | closing in favor of #2924 | 2021-01-01T17:08:34 | 2021-01-01T17:08:34 | {} | MEMBER |
vuejs | core | 753,996,619 | 2,911 | haferje | Sorry. I'm not sure why it submitted twice. | 2021-01-04T14:11:39 | 2021-01-04T14:11:39 | {} | NONE |
vuejs | core | 754,645,556 | 2,944 | HcySunYang | The Vue compiler is not a JavaScript compiler, and the state machine does not include the JavaScript syntax environment, otherwise it will be very complicated. This still doesn't work in Vue2, and I think it can be solved by configuring `delimiters`. | 2021-01-05T13:46:06 | 2021-01-05T13:46:06 | {} | MEMBER |
vuejs | core | 752,101,187 | 2,904 | liaoliao666 | > @liaoliao666 can you add a test case?
okay | 2020-12-29T14:40:18 | 2020-12-29T14:40:18 | {} | CONTRIBUTOR |
vuejs | core | 752,724,970 | 2,851 | jods4 | Aside: I haven't checked but I am pretty sure `readonly` works slightly differently?
At least you can wrap a `reactive` instance into a `readonly` one and get 2 different objects.
Not sure what happens if you call readonly on the target directly.
Simply the idea of wrapping one object in different reactive wrappe... | 2020-12-30T19:00:50 | 2020-12-30T19:00:50 | {} | CONTRIBUTOR |
vuejs | core | 753,322,329 | 2,851 | jods4 | > Either way, I'd say the current implementation is to be rated a bug as a shallowReactive should definitely not return a deep reactive proxy without any kind of warning, and vice versa. Would you agree?
I agree. I would throw in debug mode if someone attempts that.
I'm not one to encourage closed-designs and I'm a... | 2021-01-01T14:18:18 | 2021-01-01T14:18:18 | {} | CONTRIBUTOR |
vuejs | core | 753,896,374 | 2,937 | LinusBorg | Please submit a valid issue with a reproduction and description. | 2021-01-04T10:34:15 | 2021-01-04T10:34:15 | {} | MEMBER |
vuejs | core | 754,713,329 | 2,944 | longlho | So how would u deal with this scenario?
```vue
<p>{{ someFn({ a: {b: 1}}) }}</p>
```
Not sure why this issue is already closed? | 2021-01-05T15:38:39 | 2021-01-05T15:39:19 | {
"+1": 6
} | NONE |
vuejs | core | 752,044,358 | 2,908 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 40.55 KB (+0.1% 🔺) |
| runtime-dom.global.prod.js | 26.88 KB (+0.17% 🔺) |
| size-check.global.prod.js | 16.24 KB (+0.2% 🔺) | | 2020-12-29T11:33:13 | 2020-12-29T11:33:13 | {} | NONE |
vuejs | core | 752,815,228 | 2,215 | softboy99 | Hi,
after update to 3.0.5, still nothing happens, no log on console, no exception thrown. i don't know how to do next, The following is the code:
<template>
<div class="side-nav-outer-toolbar">
<header-toolbar
class="layout-header"
:menu-toggle-enabled="true"
:toggle-menu-func="toggleMenu... | 2020-12-31T01:56:45 | 2020-12-31T01:58:19 | {} | NONE |
vuejs | core | 752,963,657 | 2,910 | rhengles | @LinusBorg Here is a link to a fiddle: https://jsfiddle.net/s5dtoy7v/
Really, if you simply use a compiled render function from a template, you get this because of the `with(_ctx){}`. | 2020-12-31T13:53:19 | 2020-12-31T13:53:58 | {} | NONE |
vuejs | core | 753,900,498 | 2,931 | LinusBorg | Use a computed() property.
```js
export default {
name: "HelloWorld",
setup(props, { slots }) {
const withText = computed(() => {
const text = getFirstValidNode(slots.default?.({ withText: true }));
return !!(text && isValidElementNode(text));
});
return { withText };
},
};
... | 2021-01-04T10:42:59 | 2021-01-04T10:42:59 | {
"+1": 2,
"laugh": 1,
"rocket": 1
} | MEMBER |
vuejs | core | 754,080,924 | 2,927 | Calvin-LL | > can you add a test?
Oops forgot to add a test, just added one | 2021-01-04T16:38:22 | 2021-01-04T16:38:22 | {} | CONTRIBUTOR |
vuejs | core | 752,044,669 | 2,904 | LinusBorg | @liaoliao666 can you add a test case? | 2020-12-29T11:34:21 | 2020-12-29T11:34:21 | {} | MEMBER |
vuejs | core | 752,061,422 | 2,908 | LinusBorg | will send a new, clean one. | 2020-12-29T12:39:56 | 2020-12-29T12:39:56 | {} | MEMBER |
vuejs | core | 752,247,278 | 2,912 | posva | Wasn't this already fixed but not released? | 2020-12-29T21:25:34 | 2020-12-29T21:25:34 | {} | MEMBER |
vuejs | core | 752,759,585 | 2,910 | LinusBorg | Could you maybe explain the actual problem ? The references issue is not really helpful in understanding the context you are experiencing your issue in.
And I don't think we will accept a change that removes a warning that is otherwise considered useful from our perspective, unless we understand how it actually caus... | 2020-12-30T21:10:33 | 2020-12-30T21:10:33 | {} | MEMBER |
vuejs | core | 752,816,496 | 2,834 | edison1105 | @Mr14huashao
First of all, `invalidateJob` is to check whether the `job` of the child update is already in the queue.
If it is already in the queue, it should not be executed repeatedly. It also works if you remove `queue[i].skip = true`, but the job will be executed multiple times.this is totally unnecessary.
... | 2020-12-31T02:05:12 | 2020-12-31T02:05:12 | {} | MEMBER |
vuejs | core | 754,434,855 | 2,941 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2021-01-05T06:40:09 | 2021-01-05T06:40:09 | {} | NONE |
vuejs | core | 754,713,734 | 2,944 | glen-84 | @posva Why are you closing this issue? This is a clear and obvious bug.
As @longlho stated, placing a backslash between the braces is _not_ escaping anything, it's just avoiding the issue by preventing two braces from being positioned next to each other.
Please reopen. | 2021-01-05T15:39:20 | 2021-01-05T15:57:15 | {
"+1": 1
} | NONE |
vuejs | core | 755,122,912 | 2,950 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2021-01-06T06:58:40 | 2021-01-06T06:58:40 | {} | NONE |
vuejs | core | 751,965,959 | 2,901 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-29T06:34:56 | 2020-12-29T06:34:56 | {} | NONE |
vuejs | core | 751,984,881 | 2,215 | softboy99 | i have same problem, Nothing happens, no log on console, no exception thrown. i don't know how to to next | 2020-12-29T07:50:54 | 2020-12-29T07:50:54 | {} | NONE |
vuejs | core | 752,399,047 | 2,916 | LinusBorg | Likely a duplicate of #2715, which has been fixed but not yet released.
Can't investigate more the repo is a whole app and not boiled down to a minimum reproduction.
You might want to open an issue with `element-plus` as well. | 2020-12-30T10:02:40 | 2020-12-30T10:03:23 | {} | MEMBER |
vuejs | core | 752,860,583 | 2,919 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-31T06:23:32 | 2020-12-31T06:23:32 | {} | NONE |
vuejs | core | 752,897,461 | 2,214 | edison1105 | @softboy99
It works fine. see https://codesandbox.io/s/vuenext-v300-suspense-reactivity-forked-gmc0l?file=/src/index.js | 2020-12-31T09:08:51 | 2020-12-31T09:08:51 | {} | MEMBER |
vuejs | core | 753,492,846 | 1,914 | AlexVipond | Found another great use case for patching props inside composition functions! I was recently writing a composition function inspired by Nuxt's [Vue Meta](https://vue-meta.nuxtjs.org/) to handle SEO-related reactive updates to pages' `head` content. Here's a small sample of its use:
```js
useHead({
title: compute... | 2021-01-02T16:20:34 | 2021-01-02T16:20:34 | {} | NONE |
vuejs | core | 753,684,807 | 2,710 | bram-pkg | Any update on this? | 2021-01-03T22:23:38 | 2021-01-03T22:23:38 | {
"+1": 1,
"eyes": 11
} | NONE |
vuejs | core | 752,011,283 | 2,904 | posva | I would say `watchEffect` is different from `watch` which does observe the value: `watchEffect` tracks changes to `d`. | 2020-12-29T09:31:58 | 2020-12-29T09:31:58 | {} | MEMBER |
vuejs | core | 752,030,699 | 2,904 | LinusBorg | @posva I think he has a point here, ~~but not sure if the change actually is the right fix~~. The lack of a test to verify doesn't help here.
What's the issue?
`hasChanged(value, oldValue)` is meant to guard against triggering an effect if the new and old value being set are the same, and it *should* keep the `wa... | 2020-12-29T10:41:37 | 2020-12-29T10:50:46 | {
"+1": 1
} | MEMBER |
vuejs | core | 752,232,382 | 2,911 | LinusBorg | Duplicate of #2912 | 2020-12-29T20:34:07 | 2020-12-29T20:34:07 | {} | MEMBER |
vuejs | core | 752,263,923 | 1,731 | rhengles | Why do we want that opaque `Property undefined was accessed during render but is not defined on instance.` ?
I'm sure that that causes many people to be scratching their heads, just like I did!
It would be better if on `runtime-core/componentPublicInstance.ts`, on the function `PublicInstanceProxyHandlers.get()`,... | 2020-12-29T22:31:18 | 2020-12-29T22:31:18 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.