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 | 785,521,138 | 3,297 | edison1105 | just tip here.
`accessCache['values']` should not equal `AccessTypes.OTHER`
if `if(this.values) { }` exec before `return { values: vals, autoFocusIndex };`
the `accessCache['values']` will be set to `A... | 2021-02-25T02:04:25 | 2021-02-25T02:48:33 | {
"heart": 1
} | MEMBER |
vuejs | core | 787,045,001 | 3,320 | Ryan2128 | > looks like a solid way. Please use chat.vuejs.org for further usage questions.
Thank you, but when watch the Map directly, cb will not be called, is it a right behavior?
@LinusBorg | 2021-02-27T09:44:33 | 2021-02-27T09:49:19 | {} | NONE |
vuejs | core | 784,970,606 | 3,227 | nrgnrg | `callHook` was removed from `Transition` in #1145 bf84ac8.
Error handling is done by `BaseTransition` but `callHook` wasn't replaced with something that can call an array of functions if that's what it is given.
I'm happy to look at this but I'm just unclear on this condition `if (!(onLeave && onLeave.length > 1)... | 2021-02-24T10:20:34 | 2021-02-24T10:23:10 | {} | CONTRIBUTOR |
vuejs | core | 785,124,224 | 3,294 | LinusBorg | We could consider a better warning when setting element attributes, as the scheduler error that's thrown makes it appear to be something different, maybe. | 2021-02-24T14:43:35 | 2021-02-24T14:43:35 | {} | MEMBER |
vuejs | core | 785,466,239 | 2,906 | andrewcourtice | @yyx990803 Excellent! Thanks for the quick reply and fix 👍 | 2021-02-24T23:39:55 | 2021-02-24T23:39:55 | {} | NONE |
vuejs | core | 786,352,369 | 3,200 | longlho | ping @HcySunYang | 2021-02-26T01:47:30 | 2021-02-26T01:47:30 | {} | NONE |
vuejs | core | 786,744,438 | 1,409 | paraboul | Joining @somodevo here,
My use case (similar to closed #1826) :
* A user ends up on a router-view which has a nested router view
* The parent view needs to async load a specific state (as a ref) so it's later available to any nested view.
How it's currently done :
Parent view
```javascript
export de... | 2021-02-26T16:17:16 | 2021-02-26T21:01:13 | {} | CONTRIBUTOR |
vuejs | core | 787,017,206 | 3,318 | LinusBorg | Your description is correct, but also expected. The described scenario is not a realistic or common one, in my perception.
I would be hard to optimize this without breaking the - much more useful - behavior of evaluating slot content only when it's actually being used/rendered. | 2021-02-27T06:55:35 | 2021-02-27T06:55:35 | {} | MEMBER |
vuejs | core | 787,395,418 | 3,323 | HcySunYang | I rethink about that, the callback registered with `onInvalidate` will not be executed in SSR at all, so we only need to provide a `NOOP` instead of `onInvalidate`. | 2021-02-28T05:04:29 | 2021-02-28T05:04:29 | {
"+1": 1
} | MEMBER |
vuejs | core | 784,978,509 | 1,609 | LinusBorg | Please open a new issue this if the problem still happens on a current version (3.0.5 right now) | 2021-02-24T10:33:19 | 2021-02-24T10:33:19 | {} | MEMBER |
vuejs | core | 784,978,949 | 3,231 | LinusBorg | Closed for inactivity. Please open a new issue if you can provide more info / an aczual reproduction | 2021-02-24T10:34:02 | 2021-02-24T10:34:02 | {} | MEMBER |
vuejs | core | 785,052,053 | 1,531 | sibbng | > @sibbng this issue is quite old and was reported for a beta version. does the issue still exist for you in stable 3.0.5 ?
Yes. | 2021-02-24T12:48:57 | 2021-02-24T12:48:57 | {} | NONE |
vuejs | core | 785,335,568 | 3,296 | LinusBorg | 1. add `include: ['index.ts']` to tsconfig
2. Run `npx tsc` without any filename
Running `tsc index.ts` doesn't respect the config, for whatever reason (someone might know, I don't - never use it that way). TS docs say this command version uses "compiler defaults" which likely means it doesn't pick up `tsconfig.j... | 2021-02-24T19:59:33 | 2021-02-24T20:02:03 | {
"+1": 1
} | MEMBER |
vuejs | core | 785,418,216 | 3,056 | plehnen | @matt-snider FYI: There are cases where vue3 will output a warning that slots are accessed outside the render function. (If you try this approach with the new composition API)
More details here https://github.com/vuejs/vue-next/issues/3257 | 2021-02-24T22:10:21 | 2021-02-24T22:10:21 | {} | NONE |
vuejs | core | 785,442,443 | 2,906 | andrewcourtice | @LinusBorg @yyx990803
Just checking - is the `__VUE_PROD_DEVTOOLS__` flag now required to be defined in production builds? Just ran a production build (using webpack) after bumping to v3.0.6 and this error came up.
![image](https://user-images.githubusercontent.com/11718453/109076994-36c20380-7747-11eb-92bf-cca4... | 2021-02-24T22:59:37 | 2021-02-24T22:59:37 | {
"+1": 1
} | NONE |
vuejs | core | 785,933,325 | 3,302 | edison1105 | same issue in latest @vue/cli. | 2021-02-25T14:26:21 | 2021-02-25T14:37:04 | {} | MEMBER |
vuejs | core | 784,342,900 | 3,287 | yyx990803 | This is not really the right place for this information, as it's focused on different build formats of Vue itself.
Also, SSR externalization should be applied to all server-side dependencies + client dependencies that provide CommonJS builds, not just `@vue/server-renderer`. | 2021-02-23T16:48:37 | 2021-02-23T16:48:37 | {} | MEMBER |
vuejs | core | 784,762,766 | 3,290 | HcySunYang | Minimum reproduction, please. A minimal reproduction means "the minimum amount of code necessary to demonstrate the problem". | 2021-02-24T04:59:15 | 2021-02-24T04:59:15 | {} | MEMBER |
vuejs | core | 786,467,758 | 2,244 | Vitaminaq | 
| 2021-02-26T07:31:53 | 2021-02-26T07:31:53 | {} | NONE |
vuejs | core | 786,408,851 | 3,302 | HcySunYang | The issue is a bit like https://github.com/vuejs/vue-next/commit/376883d1cfea6ed92807cce1f1209f943a04b625, the difference is that this issue brings duplicate mounting instead of unmounting. When performing HMR updates, we deliberately fall back to the non-optimized mode, like this https://github.com/vuejs/vue-next/blob... | 2021-02-26T04:49:12 | 2021-02-26T08:08:17 | {} | MEMBER |
vuejs | core | 786,560,172 | 3,056 | plehnen | If you want to be sure that the slot is considered empty even if the content is something like `{{ emptyVariable }}` you have to check for empty text too, e.g.:
```js
export const stripEmpty = (slot, data) => {
return slot(data).filter(vnode => vnode.type !== Comment && (vnode.type !== Text || vnode.children.trim(... | 2021-02-26T10:30:43 | 2021-02-26T10:30:43 | {
"+1": 2
} | NONE |
vuejs | core | 786,670,875 | 3,315 | edison1105 | It's not a bug.this is intentional in options api.
you will see your expected use `setup`:
```javascript
setup(){
const arr = [1, 2, 3].map((num) => ({ num: ref(num) }))
arr.forEach((el) => {
console.log(el.num);
console.log(el.num.value);
});
}
``` | 2021-02-26T14:12:03 | 2021-02-26T15:21:11 | {} | MEMBER |
vuejs | core | 786,873,490 | 3,314 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/2827 | 2021-02-26T20:20:35 | 2021-02-26T20:20:35 | {} | MEMBER |
vuejs | core | 787,207,364 | 1,600 | antoniandre | @LinusBorg, @yyx990803, would be so helpful to get this PR merged in!
It is tagged as ready, reviewed and non breaking for some time and it was even supposed to ship in 3.0.6. 😢
Whitespace handling is a critical option for all the multiline slots parsing like syntax highlighters.
Thankfully Vue 2 can manage t... | 2021-02-28T00:06:28 | 2021-02-28T00:06:28 | {
"+1": 2
} | NONE |
vuejs | core | 784,761,527 | 3,289 | HcySunYang | This should be a vue-loader's issue, tracked in https://github.com/vuejs/vue-loader/issues/1778 | 2021-02-24T04:56:33 | 2021-02-24T04:56:33 | {
"+1": 1
} | MEMBER |
vuejs | core | 785,125,836 | 1,531 | LinusBorg | Thanks! | 2021-02-24T14:45:55 | 2021-02-24T14:45:55 | {} | MEMBER |
vuejs | core | 786,756,569 | 1,409 | LinusBorg | I think that should be kind of achievable by providing a ref *before* running any async operations:
```js
export default {
name: "ParentView",
async setup() {
const user = ref()
provide('user', user)
user.value = await useUser()
// ....
... | 2021-02-26T16:37:29 | 2021-02-26T16:39:22 | {
"+1": 1
} | MEMBER |
vuejs | core | 785,942,193 | 2,834 | yyx990803 | I believe #3184 provides a more robust fix for this, but thanks a lot of this PR as it provides important information for #3184 to build upon. | 2021-02-25T14:38:55 | 2021-02-25T14:38:55 | {} | MEMBER |
vuejs | core | 786,312,056 | 2,389 | jods4 | I was intrigued when I saw this added to the 3.1 plan.
I think that a `stop` concept is needed (either in addition or in replacement of `cleanup`).
The issue #2261 notes that a computed having a long-lived dependency will leak itself and all its dependencies.
Looking at WPF for prior art, the "best" (but not r... | 2021-02-25T23:57:55 | 2021-02-25T23:57:55 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 787,032,522 | 3,320 | Ryan2128 | I just now change the demo to watch the `test.test.entries()`, it works.
But is there any other way? | 2021-02-27T07:59:49 | 2021-02-27T07:59:49 | {} | NONE |
vuejs | core | 787,040,744 | 3,320 | LinusBorg | looks like a solid way. Please use chat.vuejs.org for further usage questions. | 2021-02-27T09:05:44 | 2021-02-27T09:05:44 | {} | MEMBER |
vuejs | core | 785,687,683 | 3,298 | Vitaminaq | thank you，yyds，With your help，I've solved it，but I think it should be more simplified。
```javascript
// vite.config.ts
import vue from '@vitejs/plugin-vue'
export const ssrTransformCustomDir = () => {
return {
props: [],
needRuntime: true
}
}
export default defineConfig({
plugins: [vue(
... | 2021-02-25T07:36:21 | 2021-02-25T07:36:21 | {
"+1": 9,
"heart": 5
} | NONE |
vuejs | core | 786,298,234 | 2,386 | yyx990803 | Fixed by c69f4ea8 | 2021-02-25T23:22:17 | 2021-02-25T23:22:17 | {} | MEMBER |
vuejs | core | 784,831,109 | 3,271 | HcySunYang | You can add the `emits` options in `Dummy.vue` to avoid this:
```html
<template>
<div>
{{ id }}
</div>
</template>
<script>
export default {
emits: ["dummy-event"],
props: {
id: {
type: Number,
required: true,
},
},
updated() {
console.log("Dummy updated");
... | 2021-02-24T06:40:45 | 2021-02-24T06:40:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 785,385,152 | 3,039 | yyx990803 | This introduces reliance on template literal types, which requires TS > 4.1, so I think we should avoid introducing it in a patch release.
I'm not sure if it even makes sense to bump minimum TS compatibility versions in 3.1, but I don't think there are easy ways around this. We'd be either stuck with TS 4.0 and neve... | 2021-02-24T21:08:08 | 2021-02-24T21:08:08 | {
"+1": 1
} | MEMBER |
vuejs | core | 786,775,282 | 1,409 | paraboul | @LinusBorg indeed, although there are drawbacks in both cases.
In your first example, `user` now contains a ref inside another ref (see edit below), and so needs to be unref'd in `ChildView`, which is kind of confusing.
In the second one, as you said, it no longer keeps track of the original identity.
Although... | 2021-02-26T17:10:10 | 2021-02-26T21:18:52 | {} | CONTRIBUTOR |
vuejs | core | 786,948,000 | 3,318 | lidlanca | @LinusBorg
foo and bar are async components, but **bar** will actually be loaded only after **foo** was loaded.
```
<foo><bar></bar></foo>
```
foo will be loaded mounted when its loader is resolved
but bar loader is only called after foo is resolved
so if it takes to load foo 5 seconds and bar 5 seconds... | 2021-02-26T23:27:17 | 2021-02-26T23:27:17 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 787,074,854 | 3,320 | edison1105 | works fine use `deep`
```javascript
watch(() => test.test, () => {
console.log(111)
},{deep:true})
```
or
```javascript
watch(test.test, () => {
console.log(111)
})
``` | 2021-02-27T13:43:33 | 2021-02-27T13:59:55 | {
"+1": 1
} | MEMBER |
vuejs | core | 787,370,945 | 3,323 | HcySunYang | Hey, thank you for your PR, but I think there is a better way. In SSR, we do not need to initialize `runner.options.onStop`, just change a little bit:
```js
const onInvalidate: InvalidateCbRegistrator = (fn: () => void) => {
cleanup = () => {
callWithErrorHandling(fn, instance, ErrorCodes.WATCH_CLEANU... | 2021-02-28T04:29:44 | 2021-02-28T04:29:44 | {} | MEMBER |
vuejs | core | 814,910,320 | 3,558 | 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).
---
You are not explaining at all what is the result... | 2021-04-07T13:22:22 | 2021-04-07T13:22:22 | {} | MEMBER |
vuejs | core | 815,842,690 | 3,557 | faxinwang | thank you for your codepen demo, then this may be a bug from Quasar. | 2021-04-08T13:51:38 | 2021-04-08T13:51:38 | {} | NONE |
vuejs | core | 814,785,243 | 3,552 | soc221b | Is the docs wrong? https://v3.vuejs.org/guide/migration/key-attribute.html#with-template-v-for | 2021-04-07T10:03:42 | 2021-04-07T10:03:42 | {} | NONE |
vuejs | core | 814,826,149 | 3,555 | duanlikang | Thank you for your reply. I can understand why it is designed this way.
I want to consult if there is a better solution for scenarios that depend on the order of attribute processing.
Now I just added a patch package for runtime-core. | 2021-04-07T11:14:16 | 2021-04-07T11:14:16 | {} | NONE |
vuejs | core | 815,608,388 | 3,566 | posva | It seems like Vue 2 does add them to `$options` https://jsfiddle.net/posva/p2gz45j8/ | 2021-04-08T09:29:56 | 2021-04-08T09:29:56 | {} | MEMBER |
vuejs | core | 817,095,383 | 3,452 | agileago | 
when i define functional component props it will display type errors
```
TS2322: Type '{ p1: StringConstructor; p2: NumberConstructor; onP1: { type: FunctionConstructor; }; }' is not assignable to type... | 2021-04-10T07:45:46 | 2021-04-10T07:46:17 | {} | NONE |
vuejs | core | 817,128,643 | 3,580 | mannok | @edison1105 How come the watch callback will be called synchronously? I have tried to expose the vm and executed the following in console:
```
vm.divs.push('a');
vm.divs.push('b');
vm.divs.push('c');
vm.divs.push('d');
```
It only output `there are 8 div` once. How come the mutation during `patch` is synchro... | 2021-04-10T12:25:24 | 2021-04-10T12:25:24 | {} | NONE |
vuejs | core | 817,927,446 | 3,591 | pdsuwwz | > `render` is not aware of the component, but you should use a Teleport instead (https://v3.vuejs.org/guide/teleport.html#teleport).
>
> Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions!
I know that `<teleport>` can emit components into the body... | 2021-04-12T15:56:43 | 2021-04-12T15:58:42 | {} | NONE |
vuejs | core | 818,395,120 | 2,039 | HcySunYang | This issue no longer exists in the latest version | 2021-04-13T02:59:44 | 2021-04-13T02:59:44 | {} | MEMBER |
vuejs | core | 814,815,495 | 3,552 | posva | hmm, no, they should be right... | 2021-04-07T10:54:51 | 2021-04-07T10:54:51 | {} | MEMBER |
vuejs | core | 815,603,728 | 3,562 | mannok | @LinusBorg Yes, I was stuck until I find this internal instance approach. Wish `$forceUpdate` can be exposed to developers. | 2021-04-08T09:23:22 | 2021-04-08T09:23:22 | {} | NONE |
vuejs | core | 815,609,998 | 3,567 | 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).
---
It is implemented | 2021-04-08T09:32:16 | 2021-04-08T09:32:16 | {} | MEMBER |
vuejs | core | 816,481,030 | 3,574 | posva | You need to use an arrow function or type `this` as said in the docs:
```ts
size: {
type: Number,
validator: function (this: void, x: number) { return x <= 100 } // and this validator
},
``` | 2021-04-09T07:35:34 | 2021-04-09T07:35:34 | {} | MEMBER |
vuejs | core | 816,535,332 | 3,577 | 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-04-09T08:59:55 | 2021-04-09T08:59:55 | {} | MEMBER |
vuejs | core | 817,099,019 | 3,581 | johnsoncodehk | @ygj6 this is just to show the problem, I use something like `ref: ({ foo } = useSomthing(...))` in real code, thanks. | 2021-04-10T08:17:02 | 2021-04-10T08:17:02 | {
"+1": 2
} | MEMBER |
vuejs | core | 817,274,200 | 3,580 | HcySunYang | Re:
> Supposed that the watcher's side effect would only be fired once before mount, but the console shows me 4 lines of console log at the beginning of the page which were executed from the same watcher, before that, I didn't make any mutation.
```
there are 1 div
there are 2 div
there are 3 div
there are 4 div... | 2021-04-11T09:01:36 | 2021-04-11T09:01:36 | {
"+1": 1
} | MEMBER |
vuejs | core | 814,772,923 | 3,555 | edison1105 | Vue2 is the same way.there is a reason why it was designed that way.
see https://github.com/vuejs/vue-next/issues/1318 | 2021-04-07T09:43:45 | 2021-04-07T09:45:13 | {} | MEMBER |
vuejs | core | 815,613,625 | 3,565 | posva | This seems to be working as expected, unless you want to be more explicit about what is expected in terms of style and what is happening. | 2021-04-08T09:37:24 | 2021-04-08T09:37:24 | {} | MEMBER |
vuejs | core | 816,517,259 | 3,576 | edison1105 | duplicate of https://github.com/vuejs/vue-next/issues/3294 | 2021-04-09T08:30:56 | 2021-04-09T08:30:56 | {} | MEMBER |
vuejs | core | 817,049,242 | 3,580 | edison1105 | watch() and watchEffect() effects are run before the DOM is mounted or updated so the template ref hasn't been updated when the watcher runs the effect.
see https://v3.vuejs.org/guide/composition-api-template-refs.html#watching-template-refs
```javascript
watch(
() => vm.divs,
(to) => {
... | 2021-04-10T01:28:23 | 2021-04-10T01:39:26 | {} | MEMBER |
vuejs | core | 817,277,004 | 3,586 | HcySunYang | Duplicate of https://github.com/vuejs/vue-next/issues/3068 | 2021-04-11T09:23:57 | 2021-04-11T09:23:57 | {} | MEMBER |
vuejs | core | 817,304,637 | 3,580 | mannok | So clear, Thank you @edison1105 @HcySunYang | 2021-04-11T13:03:19 | 2021-04-11T13:03:19 | {} | NONE |
vuejs | core | 817,638,340 | 3,557 | posva | Here is the correct way of setting an array of `refs`: https://v3.vuejs.org/guide/composition-api-template-refs.html#usage-inside-v-for | 2021-04-12T09:14:58 | 2021-04-12T09:14:58 | {
"+1": 1
} | MEMBER |
vuejs | core | 818,298,272 | 3,588 | Guervyl | From https://v3.vuejs.org/guide/migration/async-components.html#introduction | 2021-04-12T23:02:54 | 2021-04-12T23:02:54 | {} | NONE |
vuejs | core | 818,386,113 | 3,555 | HcySunYang | Because this behavior is the same as vue2, I wonder how weex handles similar problems? | 2021-04-13T02:32:11 | 2021-04-13T02:32:11 | {} | MEMBER |
vuejs | core | 814,969,259 | 3,557 | edison1105 | @posva
demo https://codepen.io/edison1105/pen/yLgzgxQ?editors=1010
steps:
- open Console
- click `X` of the last `tab `to remove the `tab`
I think this is not a bug
if `ref `is a function it will called when unset ref in `unmount`
```javascript
} else if (isFunction(ref)) {
callWithErrorHandling(ref... | 2021-04-07T14:38:39 | 2021-04-07T15:06:15 | {} | MEMBER |
vuejs | core | 815,481,937 | 3,562 | mannok | I found that `queueJob` is not exposed for us... and `queuePostFlushCb ` does not have the ability to de-duplicate the callback. May I know if I can use `queueJob` here? | 2021-04-08T06:19:16 | 2021-04-08T06:19:16 | {} | NONE |
vuejs | core | 815,606,167 | 3,562 | posva | > We do want people to rely on this as little as possible, which is also why we don't document anything about it's APIs - it's considered internal and more of an escape hatch for lib authors.
Yeah, what would we expose though?
```js
export function useForceUpdate() {
const instance = getCurrentInstance()
r... | 2021-04-08T09:26:54 | 2021-04-08T09:27:39 | {
"+1": 4
} | MEMBER |
vuejs | core | 815,612,708 | 3,566 | Justineo | Yeah I've checked it's how devtools currently manage to categorize properties into `data`, `computed`, etc. | 2021-04-08T09:36:06 | 2021-04-08T09:36:06 | {} | MEMBER |
vuejs | core | 816,341,211 | 3,569 | edison1105 | as a workaround add `key` to `p`:
``` javascript
<Bar>
<p key="1" v-if="true">
1
</p>
</Bar>
<Bar>
<p key="2" v-if="true">
2
</p>
</Bar>
``` | 2021-04-09T01:39:02 | 2021-04-09T01:50:43 | {} | MEMBER |
vuejs | core | 816,447,330 | 3,562 | HcySunYang | >>>
```js
export function useForceUpdate() {
const instance = getCurrentInstance()
return () => instance.proxy.$forceUpdate()
}
```
@posva , Looks great 👍 | 2021-04-09T06:34:50 | 2021-04-09T06:34:50 | {} | MEMBER |
vuejs | core | 817,108,894 | 3,580 | mannok | Thanks @edison1105 , OK I get this now. However, as the documents mentioned that
> watch() and watchEffect() effects are run before the DOM is mounted or updated
using the following codes:
```
<template>
<ul>
<li :ref="(el) => (divs[i] = el)" v-for="(item, i) in lists" :key="item">
{{ item }}
</li>... | 2021-04-10T09:42:05 | 2021-04-10T09:42:05 | {} | NONE |
vuejs | core | 815,426,745 | 3,562 | HcySunYang | Oh...sorry.... yes, that should be `instance` | 2021-04-08T03:56:16 | 2021-04-08T03:56:16 | {} | MEMBER |
vuejs | core | 815,598,853 | 3,562 | HcySunYang | Yeah, I agree with @LinusBorg | 2021-04-08T09:16:17 | 2021-04-08T09:16:17 | {} | MEMBER |
vuejs | core | 815,861,982 | 3,557 | faxinwang | I see it, showing the same error
```
vue.global.prod.js:1 TypeError: Cannot set property 'tab' of undefined
at ref (eval at ea (vue.global.prod.js:1), <anonymous>:24:35)
```
so if this is not the correct way of setting a bunch of ref，what it the correct way to do it. Or how to access the children of a spec... | 2021-04-08T14:17:06 | 2021-04-08T14:17:06 | {} | NONE |
vuejs | core | 816,638,727 | 737 | F0rsaken | I'm currently using `vue@3.0.7` and refs unwraping in arrays is still happening and array items references are changed, even on `push`. I tested it on this example:
```ts
const testObj = { f: ref(0) };
const testArr = ref<any[]>([]);
testArr.push(testOj);
console.log(isRef(testObj.f)) // true
console.log(testAr... | 2021-04-09T12:11:52 | 2021-04-09T12:11:52 | {} | NONE |
vuejs | core | 814,664,147 | 3,541 | BertieGo | > Hint.
>
> When calling `unshift/shift/splice`, etc., these methods will manipulate the original array. In the worst case, that will call the `set` trap for the array integer key **n** times, `n` represents the number of array elements, which is a time-consuming operation.
Thanks for your comment, this issue bri... | 2021-04-07T07:10:46 | 2021-04-07T07:11:36 | {} | NONE |
vuejs | core | 815,127,672 | 3,548 | jmhmd | Thanks so much for the workaround! can confirm it is working for me. | 2021-04-07T18:24:34 | 2021-04-07T18:24:34 | {} | NONE |
vuejs | core | 816,443,471 | 3,561 | HcySunYang | Currently this is expected, `<script setup>` is closed by default, see https://github.com/vuejs/rfcs/blob/script-setup-2/active-rfcs/0000-script-setup.md#closed-by-default. But the RFC about the `expose` is still under discussion https://github.com/vuejs/rfcs/pull/210. I tried to give a workaround, but the result was m... | 2021-04-09T06:26:42 | 2021-04-09T06:26:42 | {} | MEMBER |
vuejs | core | 816,776,240 | 3,548 | HcySunYang | Yeah, removing that is the correct and recommended workaround. | 2021-04-09T15:48:11 | 2021-04-09T15:48:11 | {} | MEMBER |
vuejs | core | 817,082,128 | 3,577 | tjk | I'm pretty sure this was a bug (I just ran into it too) and I think it is fixed by this patch: https://github.com/vuejs/vue-next/commit/abd129d845951737c335a80a8af6cf7b0df2f74d. It should be fixed in 3.0.11 but maybe @gezhigang1005 you have an older version of `@vue/compiler-core` still being pulled in?
(should no l... | 2021-04-10T05:30:11 | 2021-04-10T05:32:30 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 817,096,824 | 3,581 | ygj6 | @johnsoncodehk Assigning a value to `{}` is not a wise choice, because `{}==={}` returns `false` and you will never be able to use the `{}` you defined.
But I think in this case, it would be better to report an exception when compiling. | 2021-04-10T07:58:14 | 2021-04-10T07:58:14 | {} | MEMBER |
vuejs | core | 817,556,764 | 3,236 | asturur | Today this has been asking again.
I think a section on fabricJS docs for interaction with VUE could be good.
| 2021-04-12T07:23:29 | 2021-04-12T07:23:29 | {} | NONE |
vuejs | core | 815,541,155 | 3,562 | posva | `$forceUpdate()` is still there:
```js
setup() {
const instance = Vue.getCurrentInstance()
console.log(instance.proxy.$forceUpdate)
}
``` | 2021-04-08T07:55:20 | 2021-04-08T07:55:20 | {
"heart": 1
} | MEMBER |
vuejs | core | 815,855,467 | 3,557 | edison1105 | > thank you for your codepen demo, then this may be a bug from Quasar.
I don't think so. see my demo without `Quasar` still got a warning in the console.
I still think this is not a bug. | 2021-04-08T14:08:15 | 2021-04-08T14:10:41 | {} | MEMBER |
vuejs | core | 816,536,155 | 3,576 | edison1105 | Is this what you want?
```javascript
<template>
<input ref="el" :size="size" >
</template>
<script>
export default {
data () {
return {
size: 1,
}
},
mounted(){
this.$refs.el.setAttribute('size',1)
this.$refs.el.removeAttribute('size')
}
}
</script>
``` | 2021-04-09T09:01:13 | 2021-04-09T09:01:13 | {} | MEMBER |
vuejs | core | 817,100,004 | 3,583 | HcySunYang | Duplicate of https://github.com/vuejs/vue-next/issues/3238 ? | 2021-04-10T08:25:40 | 2021-04-10T08:25:40 | {} | MEMBER |
vuejs | core | 817,101,928 | 3,183 | johnsoncodehk | I think compiler has no a perfect way to solve this problem, but IDE already report error for this use case, so maybe we don't need to do anything in compiler side. | 2021-04-10T08:42:23 | 2021-04-10T08:42:23 | {} | MEMBER |
vuejs | core | 814,758,533 | 3,532 | posva | Do you have more information on where are these changes coming from? Documentation you used from api-extractor for example? | 2021-04-07T09:23:26 | 2021-04-07T09:23:26 | {} | MEMBER |
vuejs | core | 814,772,791 | 3,532 | imsunhao | demo:
https://github.com/microsoft/rushstack/blob/master/build-tests/api-extractor-scenarios/src/runScenarios.ts
Then I found that the speed increased by 10s through local test => yarn build --release | 2021-04-07T09:43:32 | 2021-04-07T09:43:32 | {} | NONE |
vuejs | core | 816,472,194 | 3,562 | LinusBorg | we could alternatively add it to context? | 2021-04-09T07:20:42 | 2021-04-09T07:20:42 | {} | MEMBER |
vuejs | core | 816,744,501 | 3,548 | jmhmd | FYI @HcySunYang when using your workaround, the same error re-appeared when using the production build (built with vite). @Alanscut solution (just removing function call) works in both dev and in production build. | 2021-04-09T14:59:10 | 2021-04-09T14:59:10 | {} | NONE |
vuejs | core | 817,073,081 | 3,562 | yyx990803 | I've actually never for once needed `forceUpdate` when using Vue 3 myself. I would rather know what use case this is absolutely needed for. | 2021-04-10T03:57:04 | 2021-04-10T03:57:17 | {
"heart": 2
} | MEMBER |
vuejs | core | 817,100,238 | 3,583 | johnsoncodehk | @HcySunYang Yes close this, thank you. | 2021-04-10T08:27:47 | 2021-04-10T08:27:47 | {} | MEMBER |
vuejs | core | 817,265,715 | 3,585 | 07akioni | > `defualt` => `default`
> your spelling is incorrect.
Sorry for that😂 | 2021-04-11T07:51:07 | 2021-04-11T07:51:07 | {} | CONTRIBUTOR |
vuejs | core | 814,867,921 | 3,556 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.46 KB (0%) |
| runtime-dom.global.prod.js | 27.51 KB (0%) |
| size-check.global.prod.js | 16.68 KB (0%) | | 2021-04-07T12:18:30 | 2021-04-07T12:18:30 | {} | NONE |
vuejs | core | 814,736,344 | 3,552 | edison1105 | ~~your repro is very weired.its refresh automatically every few seconds without doing anything in codesandbox. 🤔~~
Not all elements are re-rendered, multiple warnings are because the deleted elements have the `undefined` key at the time of `patch`. because `getTransitionRawChildren` does not filter out deleted elem... | 2021-04-07T08:58:04 | 2021-04-08T03:16:23 | {} | MEMBER |
vuejs | core | 815,429,067 | 3,562 | mannok | > Oh...sorry.... yes, that should be `instance`
by the way, I don't find a function named `queueJob`, is it the same with `nextTick`? | 2021-04-08T04:04:22 | 2021-04-08T04:04:22 | {} | NONE |
vuejs | core | 815,894,286 | 3,557 | edison1105 | I have no idea.ping @HcySunYang | 2021-04-08T14:58:59 | 2021-04-08T14:58:59 | {} | MEMBER |
vuejs | core | 817,919,059 | 3,591 | posva | `render` is not aware of the component, but you should use a Teleport instead (https://v3.vuejs.org/guide/teleport.html#teleport).
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-04-12T15:44:53 | 2021-04-12T15:44:53 | {} | MEMBER |
vuejs | core | 818,385,702 | 3,590 | HcySunYang | Does this really need a fix? For runtime-dom, we assume that it runs in a standard browser environment. | 2021-04-13T02:30:46 | 2021-04-13T02:30:46 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.