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 | 631,303,641 | 1,211 | pikax | This is arguable, personally this doesn't improve readability.
Personally I prefer to bail out as soon as possibly on the method. | 2020-05-20T07:52:32 | 2020-05-20T07:52:32 | {
"+1": 3
} | MEMBER |
vuejs | core | 626,859,012 | 1,166 | yyx990803 | Vue 3 no longer has special behavior for `v-for` refs: https://composition-api.vuejs.org/api.html#template-refs | 2020-05-11T17:57:49 | 2020-05-11T17:57:49 | {
"+1": 1
} | MEMBER |
vuejs | core | 626,880,440 | 1,165 | yyx990803 | Yeah... technically. But using both on the same element has always been discouraged. Maybe we should add a warning for it. | 2020-05-11T18:36:13 | 2020-05-11T18:36:13 | {} | MEMBER |
vuejs | core | 626,969,247 | 1,168 | yyx990803 | Closing since the repro is working fine. Also cannot reproduce locally. | 2020-05-11T21:16:29 | 2020-05-11T21:16:29 | {} | MEMBER |
vuejs | core | 627,850,541 | 1,173 | sionzee | Even when you make there only single package of Vue by replacing
```javascript
import {defineComponent} from "vue"
```
for
```javascript
const {defineComponent} = window.Vue
```
It will still keep throwing the errors. (I have checked it and there is only 1 Vue library)
The replication case is huge because I ... | 2020-05-13T09:00:04 | 2020-05-13T09:02:24 | {} | NONE |
vuejs | core | 627,872,624 | 1,173 | sionzee | I'm not able to replicate it on the git repository right now. (it is working fine) I will try to struggle it more in few hours. (I was trying it on the real project, so I have maybe forgot to change something) | 2020-05-13T09:40:35 | 2020-05-13T09:44:53 | {} | NONE |
vuejs | core | 628,428,852 | 1,180 | underfin | Yeah. I found bug and take a pr to reslove it. | 2020-05-14T06:55:19 | 2020-05-14T06:55:19 | {
"+1": 2
} | MEMBER |
vuejs | core | 629,128,098 | 1,174 | posva | You can do
```js
let app = createApp(App)
app.component('Recursive', Recursive)
``` | 2020-05-15T09:16:44 | 2020-05-15T09:16:44 | {} | MEMBER |
vuejs | core | 629,736,432 | 1,196 | yyx990803 | This is probably has to do with your tsconfig and default import. Either way, not a Vue core issue. | 2020-05-17T03:16:44 | 2020-05-17T03:16:44 | {} | MEMBER |
vuejs | core | 630,205,626 | 1,179 | yyx990803 | Sometimes redundancy in tests help identify problems more accurately. | 2020-05-18T14:06:10 | 2020-05-18T14:06:10 | {} | MEMBER |
vuejs | core | 630,431,597 | 1,205 | pikax | Thank you
There's a PR for 3.9 with this fix.
https://github.com/vuejs/vue-next/pull/1106 | 2020-05-18T20:58:17 | 2020-05-18T20:58:17 | {} | MEMBER |
vuejs | core | 631,309,407 | 1,155 | LinusBorg | they are through $attrs like today in Vue 2. | 2020-05-20T08:03:15 | 2020-05-20T08:03:15 | {} | MEMBER |
vuejs | core | 632,610,651 | 1,221 | reaink | @Justineo Thank you for your reply, I test that there is no problem in jsbin.com, but I run vite in add in `app.config.isCustomElement = tag => tag.startsWith ('xy-')` There will still be warning, this is vite problem ? | 2020-05-22T10:05:42 | 2020-05-22T10:05:42 | {} | NONE |
vuejs | core | 628,413,173 | 1,181 | zeng450026937 | Declare a prop here is for demonstrate only.
Fallthrough attrs changing cause child component re-render too.
https://jsfiddle.net/450026937/whdtnqgk/39/ | 2020-05-14T06:19:23 | 2020-05-14T06:19:23 | {} | NONE |
vuejs | core | 628,042,177 | 1,151 | underfin | Todo:
1.some test has bugs and I will commit pr and update test
2.test hooks called with arguments and transition element class state.I don't have correct solution. And this need your some help. | 2020-05-13T14:50:09 | 2020-05-14T10:03:22 | {} | MEMBER |
vuejs | core | 629,734,000 | 1,196 | underfin | Please see here https://github.com/vuejs/vue-next-webpack-preview/issues/5. | 2020-05-17T02:40:06 | 2020-05-17T02:40:06 | {} | MEMBER |
vuejs | core | 630,852,701 | 1,206 | LinusBorg | > If not could you please reopen this ticket in case there's a fix for it?
There is no fix for this in the context of this bug report, so I won't re-open. By moving the line into `setup` and out of the children, you created something that *cannot* be reactive when there's no default slot. There's not really anything... | 2020-05-19T14:22:50 | 2020-05-19T14:23:01 | {} | MEMBER |
vuejs | core | 631,038,383 | 1,209 | basvanmeurs | Thanks aztalbot, I think you're right! | 2020-05-19T19:37:40 | 2020-05-19T19:37:40 | {} | CONTRIBUTOR |
vuejs | core | 631,442,137 | 1,211 | yyx990803 | As @pikax said | 2020-05-20T12:27:46 | 2020-05-20T12:27:46 | {} | MEMBER |
vuejs | core | 632,023,343 | 1,220 | Justineo | If you don't have enough reasoning behind this, we'll just keep it as-is. If you are suggesting a change of the public API, you should create an [RFC](https://github.com/vuejs/rfcs) for it. | 2020-05-21T11:00:55 | 2020-05-21T11:00:55 | {} | MEMBER |
vuejs | core | 632,545,609 | 1,221 | Justineo | According to [the published RFC](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0009-global-api-change.md), it should be:
```js
app.config.isCustomElement = tag => tag.startsWith('xy-')
```
| 2020-05-22T07:39:16 | 2020-05-22T07:39:16 | {} | MEMBER |
vuejs | core | 628,351,490 | 1,181 | yyx990803 | Why would a component declare a prop and then never use it? Why is optimization even needed for this? Sounds useless to me. | 2020-05-14T02:40:57 | 2020-05-14T02:40:57 | {} | MEMBER |
vuejs | core | 628,517,984 | 1,181 | zeng450026937 | Please kindly let me known why this optimization is unnecessary.
In my experience, vue component is design to having it's own render scope, which is triggered by an render watcher.
But changing the fallthrough attrs of the component, also makes re-rendering triggered, which should be an wasted rending, and that is c... | 2020-05-14T09:34:11 | 2020-05-14T09:34:11 | {} | NONE |
vuejs | core | 628,962,930 | 1,181 | 450026937 | In fact, class/style falling through is the common scenario when writing a component.
For example, if we are performing a tweening animation on child component, that would be unacceptable.
Holding ref of target element can make things happy, but another scheduler is needed for separating read/write tasks, while tha... | 2020-05-15T00:57:02 | 2020-05-15T00:57:02 | {} | NONE |
vuejs | core | 626,969,039 | 1,164 | yyx990803 | FYI Vue 3 JSX props translation will be exactly the same as standard JSX. The only difference is children handling (Array instead of variadic arguments). | 2020-05-11T21:16:05 | 2020-05-11T21:16:05 | {} | MEMBER |
vuejs | core | 627,331,642 | 1,172 | LinusBorg | Change of template syntax is a pretty significant change and will require an RFC.
There's ongoing discussions here: https://github.com/vuejs/rfcs/issues/73
| 2020-05-12T13:07:11 | 2020-05-12T13:07:11 | {} | MEMBER |
vuejs | core | 629,063,516 | 1,187 | Kagashino | Well, I found the relative [rfcs](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0009-global-api-change.md#configoptionmergestrategies-behavior-change), it may help you.
There is no more `defaultStrat` in 3.0. Users must now always provide their own merge strategy functions instead of reusing built-in strateg... | 2020-05-15T06:52:06 | 2020-05-15T06:52:50 | {
"+1": 2
} | NONE |
vuejs | core | 630,214,755 | 1,175 | yyx990803 | Does #1151 contain tests for this? | 2020-05-18T14:20:49 | 2020-05-18T14:20:49 | {} | MEMBER |
vuejs | core | 630,687,385 | 1,206 | LinusBorg | This is expected from your code.
You create the `vnodes` variable once, in setup. if there's no default slot, it's initialized to an empty array.
So the `children` component that you create loops over an empty array and therefore can never collect any reactive dependencies - hence, it never re-renders.
Solutio... | 2020-05-19T09:00:46 | 2020-05-19T09:01:21 | {} | MEMBER |
vuejs | core | 631,349,448 | 1,210 | zhangzhonghe | @pikax Good job! | 2020-05-20T09:13:21 | 2020-05-20T09:13:21 | {} | MEMBER |
vuejs | core | 626,868,449 | 1,165 | rashfael | Okay, got it. That's a breaking change then? In Vue 2 it was the other way round. | 2020-05-11T18:14:52 | 2020-05-11T18:14:52 | {} | NONE |
vuejs | core | 626,870,554 | 1,157 | yyx990803 | closed via 1b946c85 | 2020-05-11T18:18:39 | 2020-05-11T18:18:39 | {} | MEMBER |
vuejs | core | 627,804,314 | 1,174 | posva | Updated to add a reproduction. Hopefully, you will use that fiddle to create a reproduction in the future 🙂 | 2020-05-13T07:32:51 | 2020-05-13T07:32:51 | {} | MEMBER |
vuejs | core | 628,372,510 | 1,082 | lzhoucs | @yyx990803 thanks for the reply. I know this ticket is closed but I do have a follow up question please. Suppose now I need to access `Tab`'s `active` prop inside `Tabs`, I found no way to do it. I've tried both:
* my original `mergeProps` approach: https://codepen.io/lzhoucs/pen/MWaBMLz
* and your `cloneVNode` app... | 2020-05-14T04:01:10 | 2020-05-14T04:03:05 | {} | NONE |
vuejs | core | 628,986,995 | 1,082 | lzhoucs | Not sure if you guys would still get notification after a ticket is closed. Just on the safe side, I opened a new ticket: https://github.com/vuejs/vue-next/issues/1186 | 2020-05-15T02:20:33 | 2020-05-15T02:24:33 | {} | NONE |
vuejs | core | 629,117,194 | 1,174 | danyadev | Oh, using import makes the component load separately, and this is noticeable when the component is first rendered, but I don’t need it
| 2020-05-15T08:53:38 | 2020-05-15T08:53:38 | {} | CONTRIBUTOR |
vuejs | core | 629,734,708 | 1,196 | Arman19941113 | > Please see here [vuejs/vue-next-webpack-preview#5](https://github.com/vuejs/vue-next-webpack-preview/issues/5).
Not this problem, I'v delared the module. | 2020-05-17T02:49:42 | 2020-05-17T02:49:42 | {} | CONTRIBUTOR |
vuejs | core | 631,290,590 | 1,210 | pikax | Good spot! Thank you.
Will PR it in a bit | 2020-05-20T07:27:51 | 2020-05-20T07:27:51 | {
"+1": 2
} | MEMBER |
vuejs | core | 631,294,315 | 1,155 | blocka | Are `attrs` automatically available in the template like `props` are? | 2020-05-20T07:34:59 | 2020-05-20T07:34:59 | {} | NONE |
vuejs | core | 760,266,691 | 3,014 | 07akioni | thanks! | 2021-01-14T15:24:10 | 2021-01-14T15:24:10 | {} | CONTRIBUTOR |
vuejs | core | 760,270,776 | 3,011 | posva | See https://v3.vuejs.org/guide/reactivity-fundamentals.html#destructuring-reactive-state | 2021-01-14T15:30:21 | 2021-01-14T15:30:21 | {} | MEMBER |
vuejs | core | 760,390,308 | 3,017 | jacekkarczmarczyk | https://github.com/vuejs/vue-next/issues/1866#issuecomment-674881439 | 2021-01-14T18:36:04 | 2021-01-14T18:36:04 | {} | CONTRIBUTOR |
vuejs | core | 760,645,845 | 3,020 | HcySunYang | I think you should put it https://github.com/vuejs/rfcs/pull/228, and discuss it there. | 2021-01-15T04:58:38 | 2021-01-15T04:58:38 | {} | MEMBER |
vuejs | core | 761,541,465 | 3,029 | HcySunYang | The reason is for type-safety, see https://github.com/vuejs/vue-next/issues/1519.
> I wonder why it works in raw h function but not in tsx. Could you please explain what does the transformation do?
As I currently know, `h` doesn't deny unknown props by default, which does cause inconsistent behavior, so for this ... | 2021-01-16T10:36:55 | 2021-01-16T10:36:55 | {} | MEMBER |
vuejs | core | 761,801,423 | 3,033 | posva | When reporting a bug always provide a reproduction https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro | 2021-01-17T12:06:30 | 2021-01-17T12:06:30 | {} | MEMBER |
vuejs | core | 762,668,249 | 2,851 | LinusBorg | Converted this back to a draft as there's both ongoing discussion about the approach itself by @jods4 and an edge case raised by @lijingfaatcumt that isn't covered yet. | 2021-01-19T07:56:37 | 2021-01-19T07:56:37 | {} | MEMBER |
vuejs | core | 763,261,071 | 2,851 | lijingfaatcumt | > 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 reacti... | 2021-01-20T01:28:31 | 2021-01-20T01:34:59 | {} | NONE |
vuejs | core | 760,747,660 | 3,022 | LinusBorg | What's proposed in the PR is not really a breaking change as it uses a new, 3rd argument to `inject()` to optionally self-inject.
However I agree that it should go through RFC, as required for new features. | 2021-01-15T08:23:32 | 2021-01-15T08:23:32 | {
"+1": 1
} | MEMBER |
vuejs | core | 761,801,595 | 3,034 | posva | Please provide a reproduction or a failing test case | 2021-01-17T12:07:56 | 2021-01-17T12:07:56 | {} | MEMBER |
vuejs | core | 762,547,764 | 2,762 | bwhyman | You should use defineAsyncComponent() declared lazy component.
```javascript
<template>
<div id="nav">
<button @click="sh = !sh">{{ sh }}</button>
<p v-if="sh">v-if</p>
<about v-if="sh" />
</div>
</template>
<script lang="ts">
import { defineAsyncComponent, defineComponent } from "vue";
// ... | 2021-01-19T01:42:44 | 2021-01-19T01:42:44 | {} | NONE |
vuejs | core | 762,579,371 | 3,034 | yesixuan | > Using a `number` would be easier to not depend on NodeJS types. A reproduction or failing test case is still necessary to move forward
I can not support a failing test case. Because if we do not clear the timer at the right time, it will not affect the normal operation of the program, but it is not benefit to the... | 2021-01-19T03:30:30 | 2021-01-19T03:30:30 | {} | NONE |
vuejs | core | 762,962,754 | 3,058 | 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-01-19T16:34:17 | 2021-01-19T16:34:17 | {} | CONTRIBUTOR |
vuejs | core | 762,715,974 | 3,052 | lijingfaatcumt | > You have a point here, but I don't think the solution is the best one.
>
> Checking the WeakMap for an existing entry is a comparatively expensive OP, which is why it's been placed _after_ the check of `ReactiveFlags.RAW` etc.
>
> Will look further into it later.
@LinusBorg i push the pr again, modify the s... | 2021-01-19T09:27:00 | 2021-01-20T01:40:51 | {} | NONE |
vuejs | core | 761,535,857 | 3,030 | LinusBorg | watchEffect is flushed in `'pre'` mode by default, which means its run *before* the DOM is updated. When working with template refs, which are updated *after* the DOM has been updated, you need to use `flush: 'post'`
```js
watchEffect(() => {
console.log("change", el.value);
}, { flush: 'post' });
... | 2021-01-16T09:47:01 | 2021-01-17T08:36:38 | {} | MEMBER |
vuejs | core | 762,212,766 | 2,851 | LinusBorg | @lijingfaatcumt What behavior would you in that case? | 2021-01-18T12:15:02 | 2021-01-18T12:15:02 | {} | MEMBER |
vuejs | core | 762,628,985 | 3,053 | 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-19T06:23:38 | 2021-01-19T06:23:38 | {} | NONE |
vuejs | core | 762,663,138 | 3,052 | posva | ~~As said in the other PR, please provide a reproduction or failing test when reporting or fixing a bug~~ Nevermind, the colors on github branch names confused me 🙃 | 2021-01-19T07:45:13 | 2021-01-19T07:47:18 | {} | MEMBER |
vuejs | core | 762,785,088 | 3,034 | yesixuan | > These timers should also be cleared in the `onBeforeUnmount` hook
done. | 2021-01-19T11:34:07 | 2021-01-19T11:34:07 | {} | NONE |
vuejs | core | 760,266,343 | 3,014 | posva | When declaring it outside you need `as const`:
```ts
const props = {
requiredValue: {
type: Array as PropType<string[]>,
required: true
}
} as const;
``` | 2021-01-14T15:23:38 | 2021-01-14T15:23:38 | {} | MEMBER |
vuejs | core | 760,272,339 | 3,008 | posva | What is this fixing? I'm closing https://github.com/vuejs/vue-next/pull/2957 in favor of this but this needs a reproduction or test case
Are you trying to fix the same thing as https://github.com/vuejs/vue-next/pull/3003 | 2021-01-14T15:32:45 | 2021-01-14T15:32:45 | {} | MEMBER |
vuejs | core | 760,359,073 | 3,016 | posva | If you have found a bug please provide a reproduction, if you have a code improvement proposal, please open a pull request | 2021-01-14T17:53:04 | 2021-01-14T17:53:04 | {} | MEMBER |
vuejs | core | 760,574,717 | 3,008 | lijingfaatcumt | > What is this fixing? I'm closing #2957 in favor of this but this needs a reproduction or test case
>
> Are you trying to fix the same thing as #3003
@posva i want add property '__v_isShallow' in a proxy object as '__v_isReadonly' because i may want to know a proxy is shallow or not, to
know if we change the d... | 2021-01-15T01:00:49 | 2021-01-15T01:07:16 | {} | NONE |
vuejs | core | 762,203,958 | 2,851 | lijingfaatcumt | > This fixes #2843
>
> We currently track reactive proxies in one WeakMap, not differentiating between normal and shallow Proxies. the same is true for readonly proxies.
>
> This means that for each target, only one kind of proxy can be created, because we use these WeakMaps to re-use existing proxies for each kn... | 2021-01-18T11:58:51 | 2021-01-18T11:58:51 | {} | NONE |
vuejs | core | 762,860,209 | 3,008 | posva | Okay, then I'm closing this in favor of https://github.com/vuejs/vue-next/pull/2851 or #3052. If you think those PR, which have tests, are missing something, please add a review. If this is unrelated, add tests and ping me so I can reopen | 2021-01-19T14:05:44 | 2021-01-19T14:05:44 | {} | MEMBER |
vuejs | core | 763,282,405 | 2,976 | yangmingshan | Removed. | 2021-01-20T02:21:59 | 2021-01-20T02:21:59 | {} | CONTRIBUTOR |
vuejs | core | 763,385,222 | 3,064 | 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-20T07:01:19 | 2021-01-20T07:01:19 | {} | NONE |
vuejs | core | 760,022,758 | 3,007 | HcySunYang | See https://github.com/vuejs/vue-next/pull/3003 | 2021-01-14T08:38:53 | 2021-01-14T08:38:53 | {} | MEMBER |
vuejs | core | 761,543,138 | 3,029 | HcySunYang | TSX has different type checking rules than `h`, here is about jsx type checking: https://www.typescriptlang.org/docs/handbook/jsx.html. For `h`, it's just a function call and has nothing to do with the type checking of jsx | 2021-01-16T10:50:11 | 2021-01-16T10:50:11 | {} | MEMBER |
vuejs | core | 761,546,886 | 2,989 | LinusBorg | I'm not too sure about this. While I get the stylistic appeal for people who (like me) like the composition API, this adds new internal complexity for us.
Conceptually, directives so far have been though to be stateless as best as possible, whereas wrapping the hooks in setup opens up the possibility of having state... | 2021-01-16T11:19:13 | 2021-01-16T11:19:13 | {} | MEMBER |
vuejs | core | 761,550,984 | 3,031 | LinusBorg | Would have been helpful to keep the repro online, but it seems you delete the branch demonstrating your issue. :/ | 2021-01-16T11:52:37 | 2021-01-16T11:52:37 | {} | MEMBER |
vuejs | core | 763,384,307 | 3,061 | skirtles-code | Using `inheritAttrs: false` should suppress the warning:
https://jsfiddle.net/skirtle/637y4au8/
Does that cover your use case? | 2021-01-20T06:59:15 | 2021-01-20T06:59:15 | {} | CONTRIBUTOR |
vuejs | core | 760,388,150 | 3,018 | diwic | Duplicate of #3017, sorry | 2021-01-14T18:32:06 | 2021-01-14T18:32:06 | {} | NONE |
vuejs | core | 760,794,019 | 3,022 | huanggm | @posva Thank you for you reply.
This PR is absolutely not a breaking change. I just add a optional parameter `selfInject`.
In fact, v3.0.2 is a breaking change.
In v3.0.1, inject function is self-inject by default. But in v3.0.2, inject function inject from parent by default and I have no way to inject from se... | 2021-01-15T09:57:36 | 2021-01-15T09:57:36 | {
"+1": 2
} | NONE |
vuejs | core | 760,978,910 | 3,024 | Liwoj | That is nice workaround for easy example like this but what if you get some complicated (and maybe nested) structure from some 3rd party lib totally independent from Vue?
The fact that same code worked just fine in Vue 2 (leaving the prop non-reactive) is making it even worse as people will start migrating and [now... | 2021-01-15T14:38:12 | 2021-01-15T14:38:12 | {
"+1": 18
} | NONE |
vuejs | core | 762,038,758 | 3,043 | 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-18T07:17:01 | 2021-01-18T07:21:55 | {} | NONE |
vuejs | core | 762,156,219 | 3,044 | HcySunYang | I still think that this requires a real use case, rather than a simple code demonstration. I don’t see what scenarios users need to care about whether the data is shallow or not. | 2021-01-18T10:36:29 | 2021-01-18T10:36:29 | {
"+1": 5
} | MEMBER |
vuejs | core | 762,608,324 | 3,050 | HcySunYang | You should import and register the `DialogBase` component in the `TeleportDialog`, see: https://codesandbox.io/s/purple-browser-yb7r6?file=/src/components/TeleportDialog.vue | 2021-01-19T05:21:27 | 2021-01-19T05:21:27 | {} | MEMBER |
vuejs | core | 762,664,978 | 3,044 | lijingfaatcumt | > I still think that this requires a real use case, rather than a simple code demonstration. I don’t see what scenarios users need to care about whether the data is shallow or not.
其实我觉得isReadonly和isShallow类似 | 2021-01-19T07:49:27 | 2021-01-19T07:49:27 | {} | NONE |
vuejs | core | 762,721,446 | 3,034 | HcySunYang | These timers should also be cleared in the `onBeforeUnmount` hook | 2021-01-19T09:36:33 | 2021-01-19T09:36:33 | {} | MEMBER |
vuejs | core | 760,550,508 | 3,015 | westhom | > I would say this should be documented
Definitely, should be added to the migration guide since it's a 2 -> 3 breaking change. | 2021-01-14T23:50:50 | 2021-01-14T23:50:50 | {
"+1": 6
} | NONE |
vuejs | core | 760,720,006 | 2,989 | cc-max | The so-called composition API, in order to solve the phenomenon that the option API causes the same function code to be scattered, and the related function codes are organized together in an orderly manner, and the custom-directive support the composition API. How should it be achieved? | 2021-01-15T07:58:11 | 2021-01-15T07:58:11 | {} | NONE |
vuejs | core | 760,794,939 | 3,024 | posva | You can use `markRaw` to tell Vue to skip any property:
```js
Object.defineProperty(outer, "prop", {
value: markRaw(inner),
writable: false,
configurable: false,
});
``` | 2021-01-15T09:59:25 | 2021-01-15T09:59:25 | {
"+1": 3,
"hooray": 1
} | MEMBER |
vuejs | core | 762,038,566 | 3,042 | 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-18T07:16:34 | 2021-01-18T07:16:34 | {} | NONE |
vuejs | core | 762,926,887 | 3,056 | plehnen | https://forum.vuejs.org/t/how-to-determine-if-slot-is-empty-in-vue3/109154 | 2021-01-19T15:42:30 | 2021-01-19T15:42:30 | {} | NONE |
vuejs | core | 760,006,222 | 2,993 | LinusBorg | Can't say anything about that with a one-liner description. Feel free to open a new issue if you have a reproduction going. | 2021-01-14T08:08:02 | 2021-01-14T08:08:02 | {} | MEMBER |
vuejs | core | 760,396,256 | 3,017 | posva | > may I ask that it should be clearly stated in the documentation?
You should propose the change with a PR on the docs-next repository! | 2021-01-14T18:47:29 | 2021-01-14T18:47:29 | {} | MEMBER |
vuejs | core | 762,126,421 | 3,044 | posva | What is the usecase? | 2021-01-18T09:48:02 | 2021-01-18T09:48:02 | {} | MEMBER |
vuejs | core | 762,300,565 | 3,047 | LinusBorg | the data you ask for doesn't have an `author` field (at least not all of them do), so `project.author.username` throws an error:
| 2021-01-18T14:55:29 | 2021-01-18T14:55:29 | {} | MEMBER |
vuejs | core | 759,439,043 | 3,001 | posva | You can use single quotes as a workaround:
```vue
<div id="app">
<list :model="{
widgets: [
{
name: 'Test',
content: '<strong>Bold Text</strong>' }
]
}"></list>
</div>
``` | 2021-01-13T13:11:22 | 2021-01-13T13:11:22 | {} | MEMBER |
vuejs | core | 759,862,961 | 2,907 | happydoop | Same problem.
I need to dynamically create lots of vueApp in my project, and I use js-lru to cache, as they are evicted from the cache, I unmount and delete, but it doesn't help. | 2021-01-14T01:24:05 | 2021-01-14T01:24:05 | {} | NONE |
vuejs | core | 760,239,102 | 3,010 | posva | I think you should type the computed property return type like said above | 2021-01-14T14:41:26 | 2021-01-14T14:41:26 | {
"+1": 3
} | MEMBER |
vuejs | core | 760,239,386 | 3,013 | posva | See https://github.com/vuejs/vue-next/issues/3010#issuecomment-760237694 | 2021-01-14T14:41:53 | 2021-01-14T14:41:53 | {} | MEMBER |
vuejs | core | 760,680,752 | 3,020 | liaoliao666 | > vuejs/rfcs#228
yep, thankssss | 2021-01-15T06:23:00 | 2021-01-15T06:23:00 | {} | CONTRIBUTOR |
vuejs | core | 761,535,467 | 3,028 | LinusBorg | I agree.
Generally, a new feature like this, that wants to add a new built-in component, would need to go through the RFC process anyway (https://github.com/vuejs/rfcs) | 2021-01-16T09:43:42 | 2021-01-16T09:43:42 | {} | MEMBER |
vuejs | core | 761,542,610 | 3,029 | 07akioni | In my original recognition I thought `tsx` just do a raw transformation from `<div onClick={null} />` to `h('div', { onClick: null })` and do the identical type checking. However, currently it works differently in typescript (when building & editing). What's the reason of the behavior? | 2021-01-16T10:45:23 | 2021-01-16T10:45:23 | {} | CONTRIBUTOR |
vuejs | core | 760,237,694 | 3,010 | HcySunYang | Oh, missed the information here: https://vuejs.org/v2/guide/typescript.html#Annotating-Return-Types, this issue can be closed.
Edit: related https://github.com/vuejs/vetur/issues/2373 | 2021-01-14T14:39:10 | 2021-01-14T14:40:39 | {} | MEMBER |
vuejs | core | 760,412,926 | 3,016 | veaba | just like that:
```ts
var a = {}
var b = a
a===b // true
```
I got.
But I still think something is not quite right. 😄
| 2021-01-14T19:19:31 | 2021-01-14T19:22:45 | {} | MEMBER |
vuejs | core | 761,301,220 | 3,027 | 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-01-16T03:03:37 | 2021-01-16T03:03:37 | {} | CONTRIBUTOR |
vuejs | core | 761,395,333 | 3,028 | edison1105 | This should be a feature of some UI Library(e.g. Element-plus), you can also implement a `match-media` Component easily and publish to NPM.
IMO,Vue does not need to have this feature built in. | 2021-01-16T04:42:28 | 2021-01-16T04:42:28 | {} | MEMBER |
vuejs | core | 763,383,688 | 3,023 | dependabot-preview[bot] | Superseded by #3062. | 2021-01-20T06:57:53 | 2021-01-20T06:57:53 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.