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 | 1,609,233,731 | 8,658 | slothvips | Well.I understand.😁 | 2023-06-27T10:31:47 | 2023-06-27T10:31:47 | {} | NONE |
vuejs | core | 1,615,826,419 | 8,685 | Justineo | Hi, thanks for your interest but Github issues are for bug reports and feature requests only.
Please ask questions in our Discussions section (which [you already did](https://github.com/vuejs/core/discussions/8683)). | 2023-07-01T10:07:15 | 2023-07-01T10:07:15 | {} | MEMBER |
vuejs | core | 1,616,427,582 | 8,682 | LinusBorg | Closing this here as its about the language tools | 2023-07-02T07:47:25 | 2023-07-02T07:47:25 | {} | MEMBER |
vuejs | core | 1,602,598,505 | 4,566 | nicooprat | Thanks for the clear explanations Linus.
We had the issue while migrating to ElementPlus through the compat build, and we fixed it like this:
```ts
// main.ts
import { ElForm } from 'element-plus';
ElForm.compatConfig = {
...ElForm.compatConfig,
INSTANCE_LISTENERS: false,
};
```
Then we can still ... | 2023-06-22T13:00:32 | 2023-06-22T13:00:32 | {
"+1": 3
} | NONE |
vuejs | core | 1,603,875,593 | 8,629 | LinusBorg | the code between `{{ }}` is a Javascript expression. So you can use a JS block comment:
```html
<template>
<div>
<p>{{ /* test */ message }}</p>
</div>
</template>
``` | 2023-06-23T07:51:07 | 2023-06-23T07:51:25 | {} | MEMBER |
vuejs | core | 1,606,526,300 | 8,509 | smallflyman | > duplicate? [github.com/vuejs/core/issues/5603](https://github.com/vuejs/core/issues/5603)
I think so | 2023-06-26T03:07:51 | 2023-06-26T03:07:51 | {} | NONE |
vuejs | core | 1,606,583,876 | 5,724 | so1ve | @juzser I tested locally and this problem does not occur. 😄 | 2023-06-26T04:43:12 | 2023-06-26T04:43:12 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,607,076,064 | 8,633 | baiwusanyu-c | I think this should be a problem with `language-tools` | 2023-06-26T09:30:37 | 2023-06-26T09:30:37 | {} | MEMBER |
vuejs | core | 1,608,956,051 | 8,604 | so1ve | It's a language-tools issue. | 2023-06-27T07:34:39 | 2023-06-27T07:34:39 | {} | MEMBER |
vuejs | core | 1,609,229,338 | 8,658 | sxzz | But only `runtime-core` used this function. Currently we needn't move it to shared. | 2023-06-27T10:29:09 | 2023-06-27T10:29:09 | {} | MEMBER |
vuejs | core | 1,609,260,883 | 8,655 | shengxinjing | > 官方不是都已经禁用`undefined`了吗? 是不是意味着 `undefined`推荐用`void`替代
我跑lint和build没出啥问题 | 2023-06-27T10:50:29 | 2023-06-27T10:50:29 | {} | CONTRIBUTOR |
vuejs | core | 1,609,502,398 | 8,604 | s-montigny-desautels | It's in `tsx` files. Isn't the language-tools for `vue` files only? | 2023-06-27T13:24:47 | 2023-06-27T13:24:47 | {} | CONTRIBUTOR |
vuejs | core | 1,614,038,935 | 7,216 | guaqiu5 | There is now progress did？ | 2023-06-30T02:47:28 | 2023-06-30T02:47:28 | {} | NONE |
vuejs | core | 1,603,697,177 | 8,592 | zqran | It is worth mentioning that hoist will take effect when using reference:
```ts
// foo.ts
export const defaults = { baz: false }
```
```ts
import { defaults } from './foo'
const props = withDefaults(defineProps<{bar: boolean}>(), defaults)
// defaults is used:
console.log(defaults)
defaults.baz = true
`... | 2023-06-23T05:24:14 | 2023-06-23T05:28:15 | {} | CONTRIBUTOR |
vuejs | core | 1,604,285,188 | 7,828 | nieyuyao | I had the same issue. | 2023-06-23T13:26:28 | 2023-06-23T13:26:28 | {
"+1": 5
} | CONTRIBUTOR |
vuejs | core | 1,613,979,986 | 8,656 | edison1105 | <s>I feel this is a bug. without `template` it works [see](https://play.vuejs.org/#eNp9U11vmzAU/StXzkNeWlhVKZoYi7ROlbZp6qZtj7y4cAF3xrZsk6ar8t93MRAgafsWnw/fcw/OM/tkTLRrkSUsdbkVxoND35ptpkRjtPVwwx1+50+69VBa3cA6iieos64zlca9l1x08NgYyT3SCSCdxOFMyMjDqkZeoB1wYuqr7Re0CI2oag/3CBwMrxC88BLTmOjhing24+TW6TazvdO0Tq0f07hb6MzZAQNstpPuL... | 2023-06-30T01:10:41 | 2023-06-30T01:18:57 | {} | MEMBER |
vuejs | core | 1,603,962,596 | 8,630 | LinusBorg | This is not an issue. Moving to discussions | 2023-06-23T09:00:31 | 2023-06-23T09:00:31 | {} | MEMBER |
vuejs | core | 1,605,299,602 | 7,499 | yangwao | > Hey, how is this standing?
Hey, I'm back to check on this after a few months; any updates? Any way we can help speed up this @LinusBorg ? | 2023-06-24T07:40:24 | 2023-06-24T07:40:24 | {
"+1": 1
} | NONE |
vuejs | core | 1,606,060,765 | 8,105 | kikuchan | After deep investigation, I've finally found the solution.
```js
--- packages/runtime-core/src/renderer.ts
+++ packages/runtime-core/src/renderer.ts
@@ -2035,6 +2035,7 @@ function baseCreateRenderer(
if (needTransition) {
if (moveType === MoveType.ENTER) {
transition!.beforeEnter(el!)
+ ... | 2023-06-25T12:11:20 | 2023-06-25T12:11:20 | {
"+1": 4,
"eyes": 1
} | NONE |
vuejs | core | 1,606,071,232 | 8,338 | Alfred-Skyblue | 👀 | 2023-06-25T12:45:57 | 2023-06-25T12:45:57 | {} | MEMBER |
vuejs | core | 1,607,089,601 | 8,633 | baiwusanyu-c | Maybe yes, you know that there have been many updates to vue's repl recently, which uses `monaco-valor`. I tried in `monaco` everything works fine and in `monaco-valor` have the same problem | 2023-06-26T09:38:30 | 2023-06-26T09:38:30 | {} | MEMBER |
vuejs | core | 1,607,736,990 | 8,640 | toplyb | em... I mean when i use this component and enter 'type="success"', i cant get TypeScript syntax hints. But in this compoent, i had set the type of 'type' with 'success' or 'error' or 'warn'. | 2023-06-26T15:37:45 | 2023-06-26T15:37:45 | {} | NONE |
vuejs | core | 1,610,393,232 | 3,870 | kushagharahi | I think the crux of the problem is that Vue3 will not hydrate prerendered HTML
In Vue2 there was a kind of hack to add `data-server-rendered="true"` to the dom element that Vue mounts to in your prerendered HTML. Then Vue2 would hydrate that prerendered HTML.
Now in Vue3 there is no such option. So static sites ... | 2023-06-28T00:15:25 | 2023-06-28T00:15:25 | {} | NONE |
vuejs | core | 1,615,356,578 | 4,314 | NJgx | Any update on this？ | 2023-07-01T02:04:14 | 2023-07-01T02:04:14 | {
"+1": 3
} | NONE |
vuejs | core | 1,602,203,118 | 8,617 | LinusBorg | You are *not* actually updating the ref value. it's `false` before clicking the checkbox, and after you update it, it's still `false` when you cancel the prompt. So Vue does not have a reason to re-render. Nothing changed.
But the HTML Element did change already. So that's the reason why your data is now out of sync... | 2023-06-22T08:09:39 | 2023-06-22T08:14:10 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,603,492,218 | 8,595 | yyx990803 | This has been discussed in the RFC repo: https://github.com/vuejs/rfcs/discussions/500 | 2023-06-23T01:00:59 | 2023-06-23T01:00:59 | {} | MEMBER |
vuejs | core | 1,605,887,868 | 8,638 | skirtles-code | I originally posted this as a comment on #8579, but I'll move my comment here instead. The minimal reproduction below is effectively the same as the one on this issue, but I think the second example helps to illustrate how the problem can happen in a slightly more realistic scenario.
---
I just encountered a simi... | 2023-06-25T06:04:18 | 2023-06-25T06:04:18 | {} | CONTRIBUTOR |
vuejs | core | 1,607,421,336 | 8,647 | Vanilagy | Workarounds for I've found for this are:
- Initializing with the unproxied elements:
```ts
const set = reactive(new Set(items.map(toRaw)))
```
- Manually initializing the Set using a loop:
```ts
const set = reactive(new Set())
for (const item of items) set.add(item)
``` | 2023-06-26T13:00:21 | 2023-06-26T13:01:53 | {} | NONE |
vuejs | core | 1,609,637,677 | 8,650 | so1ve | My fault. We can use v-bind actully. | 2023-06-27T14:35:42 | 2023-06-27T14:35:42 | {} | MEMBER |
vuejs | core | 1,612,694,746 | 8,676 | yoshi-pi | In this case, I believe re-rendering will occur. This is because Vue.js's reactive system, particularly ReactiveEffect, watches reactive data accessed during rendering. In addition, ":class" accesses properties of the specified object in the attribute value, and since that property is a ref object, it triggers re-rende... | 2023-06-29T09:21:17 | 2023-06-29T09:37:05 | {} | NONE |
vuejs | core | 1,601,975,251 | 8,623 | sxzz | I guess it should be moved to https://github.com/vuejs/language-tools
/cc @johnsoncodehk | 2023-06-22T03:53:23 | 2023-06-22T03:53:23 | {} | MEMBER |
vuejs | core | 1,602,408,272 | 6,587 | masquevil | same trouble | 2023-06-22T10:35:14 | 2023-06-22T10:35:14 | {} | NONE |
vuejs | core | 1,603,687,049 | 8,592 | sxzz | Even tough it's `const`, we can still modify the property value of the object.
```ts
const obj = { a : 1 }
obj.a = 2
```
---
I think the better way for avoiding confusing is that local variables as parameters of `withDefault` should never used outside of `withDefault`.
For example we only support this case
`... | 2023-06-23T05:08:31 | 2023-06-23T05:08:54 | {} | MEMBER |
vuejs | core | 1,609,817,535 | 8,641 | kikuchan | I'm sorry, I've found that the 1st patch was wrong. (sometimes didn't work)
This time, make the `anchor` selection step robust. It works perfectly, so far.
The last patch could be PoC, but it surely means the bug exists nearby.
Noticeable point is, `unmount` and `move` could trigger `remove` operation multiple t... | 2023-06-27T16:02:41 | 2023-06-27T16:02:41 | {} | NONE |
vuejs | core | 1,610,889,113 | 8,565 | Alfred-Skyblue | cc @sxzz 👀 | 2023-06-28T07:10:56 | 2023-06-28T07:10:56 | {
"eyes": 1
} | MEMBER |
vuejs | core | 1,612,637,100 | 8,676 | LinusBorg | This likely won't be happening/be possible.
What you are describing in the status quo is simply how Vue's Reactivity at its very core works: a component re-renders when a reactive dependency *that is being used in the template* is changed. if you use a nonreactive object in the template - for class attributes, child... | 2023-06-29T08:38:01 | 2023-06-29T08:38:01 | {} | MEMBER |
vuejs | core | 1,615,850,524 | 8,682 | KawaiiZapic | > use transition-group
What if:
```vue
<script>
const list=[{
id:0,
type: "user"
}]
</script>
<template>
<transition v-for=item in list :key=item.id :name="'transition-'+item.type"/>
</template>
``` | 2023-07-01T11:03:16 | 2023-07-01T11:03:31 | {} | NONE |
vuejs | core | 1,616,506,679 | 8,682 | KawaiiZapic | > Closing this here as its about the language tools
I don't think it is a language tools problem.
this is caused by bad type definition in core, we need modify the type definition of `FunctionalComponent` to inherit some Vue-reserved props like `:key` | 2023-07-02T09:15:19 | 2023-07-02T09:15:48 | {
"+1": 1
} | NONE |
vuejs | core | 1,619,207,655 | 7,542 | jcuenod | Not sure if it's the same issue, but I'm mapping through a list of words to create clickable spans. Each word should be separated by various "before" and "after" text that does not need to be in its own node. Leading and trailing whitespace is elided in these cases. | 2023-07-03T22:14:18 | 2023-07-03T22:14:18 | {} | NONE |
vuejs | core | 1,623,881,428 | 8,727 | shareefhadid | > Your case is opposite of mine : #7999. Also I've seen your question on stackoverlfow, let's discuss there in the comments.
Thank you for sharing :) I am not sure if this is a duplicate exactly, I think we are talking about something very similar, but I would hope the Vue team would consider going beyond just class... | 2023-07-06T15:28:50 | 2023-07-06T15:28:50 | {
"+1": 1
} | NONE |
vuejs | core | 1,628,792,610 | 8,750 | LinusBorg | We are aware that this can be an issue, but it also has its advantages (i.e. positioning children etc easily) - also it's documented behavior that we can't change outside of a major release.
https://vuejs.org/api/sfc-css-features.html#child-component-root-elements | 2023-07-10T11:39:33 | 2023-07-10T11:39:33 | {} | MEMBER |
vuejs | core | 1,632,580,012 | 8,487 | mattersj | @dodgex I think you're talking about slightly different issue here:
Since 3.3 (probably, specifically `alpha.13` as you mentioned) Vue has changed the way types get resolved and this is also true for `InjectionKey`. That means that previously (<= `alpha.12`), `InjectionKey` wasn't resolved properly and the type was ... | 2023-07-12T13:56:58 | 2023-07-12T14:07:06 | {} | CONTRIBUTOR |
vuejs | core | 1,633,196,888 | 6,859 | obj63mc | Checking if there are any updates for this, vue shouldn't really be breaking native browser functionality. | 2023-07-12T20:49:50 | 2023-07-12T20:49:50 | {} | NONE |
vuejs | core | 1,633,538,740 | 8,764 | lv-z-l | What I want to express is that the indexOf, including lastIndexOf, traversed through each track of the group, creates an additional collection of dependencies. For example, indexOf('d', 2), indexes 0 and 1 should not collect dependencies.
```ts
;(['includes', 'indexOf', 'lastIndexOf'] as const).forEach(key => {
... | 2023-07-13T04:46:51 | 2023-07-13T04:46:51 | {} | NONE |
vuejs | core | 1,633,654,113 | 7,240 | LinusBorg | > @LinusBorg Can please elaborate on that? What's does "simply don't support" mean? The Proxy doesn't have access to private members but that's by design -- [developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy#no_private_property_forwarding](https://developer.mozilla.org/en-US/docs/Web/JavaSc... | 2023-07-13T06:43:36 | 2023-07-13T06:43:36 | {} | MEMBER |
vuejs | core | 1,624,579,602 | 5,836 | MarkSky | > @MarkSky The PR is not merged.
I know.
I just create a project and use your playground code.
but the <Transition> is not work in my project. | 2023-07-07T02:58:13 | 2023-07-07T02:58:13 | {} | NONE |
vuejs | core | 1,625,102,566 | 8,738 | shengxinjing | Because you used the item as a key, the input changed and rerender | 2023-07-07T09:08:28 | 2023-07-07T09:08:28 | {} | CONTRIBUTOR |
vuejs | core | 1,632,406,072 | 8,487 | mattersj | @dodgex I believe that this bug has been around for a while since the affected part of the code hasn't been changed in ~4 years. It seems you can reproduce it on almost every 3.x version, not only 3.3.x. | 2023-07-12T12:04:24 | 2023-07-12T12:04:24 | {} | CONTRIBUTOR |
vuejs | core | 1,627,680,425 | 5,952 | beejaz | Would be nice if this bug could be squeezed. Stuck in Nuxt3 workarounds for now. | 2023-07-09T10:55:04 | 2023-07-09T10:55:04 | {
"+1": 5
} | NONE |
vuejs | core | 1,631,946,364 | 8,753 | sxzz | Duplicate of #8607 | 2023-07-12T06:49:54 | 2023-07-12T06:49:54 | {} | MEMBER |
vuejs | core | 1,631,975,336 | 8,755 | Shyam-Chen | `defineComponent<T>()` | 2023-07-12T07:14:57 | 2023-07-12T07:14:57 | {} | CONTRIBUTOR |
vuejs | core | 1,632,253,762 | 8,487 | dodgex | I was about to create an issue for this, but last minute i found this one. From my testing the bug was introduced in `3.3.0-alpha.13`, alpha 12 was still working.
would love to see this fixed :) | 2023-07-12T10:30:11 | 2023-07-12T10:30:11 | {} | NONE |
vuejs | core | 1,632,770,083 | 8,769 | LinusBorg | And here's why it only happens in dev, *if I recall correctly*:
In prod, we do a finer-grained props update - ~~we do a looseEqual check to catch precisely the case I described before: elements created in the template~~ the compiler knows which props are stable (like your static inline array in `:a=""`) and which c... | 2023-07-12T15:37:30 | 2023-07-12T20:53:25 | {} | MEMBER |
vuejs | core | 1,633,910,281 | 8,743 | Shyam-Chen | https://github.com/vuejs/language-tools/issues/3292 | 2023-07-13T09:41:09 | 2023-07-13T09:41:09 | {} | CONTRIBUTOR |
vuejs | core | 1,619,729,405 | 8,549 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 73cd394f53f863ea46c7efcf4a3a8ca4f0d1260e |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2023-07-04T07:56:36 | 2023-07-04T07:56:36 | {} | NONE |
vuejs | core | 1,620,094,600 | 5,407 | cope | First node in the `<template>` must be a div (*or some other valid element, but div works for me, so...*)
```
<template>
<div>
...
</div>
</template>
```
If you add somethins else into <template> but outside of the wrapping `<div>`, this error occurs.
I do not know what, if any, offending nodes may b... | 2023-07-04T11:45:26 | 2023-07-04T11:48:17 | {
"+1": 2
} | NONE |
vuejs | core | 1,621,172,036 | 8,715 | LinusBorg | I think you're talking about this documented caveat:
https://vuejs.org/guide/essentials/reactivity-fundamentals.html#caveat-when-unwrapping-in-templates
According to this docuemented behaviour, what you need to do is this use `.value` like in other places, too:
```html
<span v-if="query.isLoading.value">
``... | 2023-07-05T07:18:45 | 2023-07-05T07:18:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,628,614,247 | 1,927 | jerrywu001 | Sometimes `resolveComponet` is not applicable, for example, there are some globally registered components (ComA, ComB, ComC,...), and then use them with dynamic components through the `h function`
or just like:
- A toast tool in node_modules， the source code:
![image](https://github.com/vuejs/core/assets/125... | 2023-07-10T09:50:11 | 2023-07-10T10:58:56 | {
"+1": 2
} | NONE |
vuejs | core | 1,630,594,423 | 8,544 | yyx990803 | manually upgraded in 2a2810c7 due to conflicts | 2023-07-11T10:44:40 | 2023-07-11T10:44:40 | {} | MEMBER |
vuejs | core | 1,631,780,241 | 7,812 | yyx990803 | #8535 provides a more fundamental fix, but still thank you for the PR! | 2023-07-12T03:04:12 | 2023-07-12T03:04:12 | {} | MEMBER |
vuejs | core | 1,632,022,742 | 8,764 | lv-z-l | If this is an optimization point that needs to be modified, hopefully you can assign it to me to complete.
| 2023-07-12T07:52:12 | 2023-07-12T07:52:12 | {} | NONE |
vuejs | core | 1,632,538,268 | 5,297 | hokkaido | @LinusBorg The default warn handler does not follow that pattern tho, it allows for instance vue-router to create copious amounts of warnings outside of the mount cycle without any way to ignore them. | 2023-07-12T13:32:13 | 2023-07-12T13:32:13 | {} | NONE |
vuejs | core | 1,633,345,554 | 8,760 | Shyam-Chen | @SunnyCrypto Which Vanilla Lib are you using? I use Highcharts. Its data cannot be reflected directly, but I can still re-render it through Watch. | 2023-07-12T23:53:01 | 2023-07-12T23:53:01 | {} | CONTRIBUTOR |
vuejs | core | 1,633,718,451 | 7,240 | LinusBorg | > But, isn't a class instance just an object with methods on it?
Not really. Since ES6, classes are a distinct thing in JS. One of those distinctions is: classes support native private fields.
> By "POJO" you mean I can't use some object constructed from a class constructor?
I'ts recommended not to. Though usi... | 2023-07-13T07:32:27 | 2023-07-13T07:32:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,633,884,213 | 8,766 | Shyam-Chen | Use `fetch` | 2023-07-13T09:24:32 | 2023-07-13T09:24:32 | {} | CONTRIBUTOR |
vuejs | core | 1,619,964,747 | 8,706 | Shyam-Chen | Use `FadeTransition` instead. | 2023-07-04T10:15:51 | 2023-07-04T10:16:58 | {} | CONTRIBUTOR |
vuejs | core | 1,619,341,390 | 8,303 | lixiaofa | @xiaoxiangmoe @arpowers
Have you solved it? I also encountered this problem， In CICD. local is OK.
https://github.com/lixiaofa/fast-plus/actions/runs/5443372337/jobs/9900013548 | 2023-07-04T01:45:20 | 2023-07-05T01:46:55 | {
"+1": 2
} | NONE |
vuejs | core | 1,621,546,607 | 8,706 | Laslo89 | To make my problem a bit clearer I have kept the example of the transition component simple. In fact, I use it in such a way that a transition name is passed as prop, which then dynamically decides which transition is executed. I think the name BaseTransition is appropriate and I don't plan to change it. Especially sin... | 2023-07-05T11:14:20 | 2023-07-05T11:14:20 | {
"+1": 1
} | NONE |
vuejs | core | 1,624,573,639 | 5,836 | edison1105 | @MarkSky The PR is not merged. | 2023-07-07T02:47:56 | 2023-07-07T02:47:56 | {} | MEMBER |
vuejs | core | 1,626,910,008 | 5,196 | filefi | > ```js
> (function() {
> 'use strict';
> unsafeWindow.Vue = Vue // replace window with unsafeWindow
> Vue.createApp({
> data() {
> return {
> foo: 'bar'
> }
> },
> template: '{{ foo }}'
> }).mount('#app');
> })();
> ```
repla... | 2023-07-08T08:24:37 | 2023-07-08T08:24:37 | {
"+1": 1
} | NONE |
vuejs | core | 1,631,795,128 | 8,757 | baiwusanyu-c | I think build related issues, I think more likely a problem with vite, you can open an issue in vite | 2023-07-12T03:29:11 | 2023-07-12T03:29:11 | {} | MEMBER |
vuejs | core | 1,632,463,773 | 8,769 | Shyam-Chen | Can't reproduce it. | 2023-07-12T12:44:12 | 2023-07-12T12:44:12 | {} | CONTRIBUTOR |
vuejs | core | 1,632,476,298 | 8,760 | Shyam-Chen | You need to avoid using `$forceUpdate`. You can use `watch` or `watchEffect` to re-render based on data changes. | 2023-07-12T12:53:07 | 2023-07-12T12:55:09 | {} | CONTRIBUTOR |
vuejs | core | 1,633,447,020 | 7,240 | sgpinkus | > FWIW, we always recommend to use POJOs for reactive state. We need to be more explicit about this specific hard limitation in the docs, though
The docs I've read explicitly recommend adding methods for stuff:
> To ensure the state-mutating logic is centralized like the state itself, it is recommended to define ... | 2023-07-13T02:27:40 | 2023-07-13T02:35:02 | {} | NONE |
vuejs | core | 1,633,445,646 | 7,240 | sgpinkus | > ES6 proxies simply don't support private fields which is a huge PITA.
@LinusBorg Can please elaborate on that? What's does "simply don't support" mean? The Proxy doesn't have access to private members but that's by design -- https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy#no_... | 2023-07-13T02:25:53 | 2023-07-13T02:36:07 | {} | NONE |
vuejs | core | 1,629,035,232 | 8,753 | Jungzl | close #6001 | 2023-07-10T14:03:29 | 2023-07-10T14:03:29 | {} | NONE |
vuejs | core | 1,630,470,644 | 8,734 | mav-rik | @LinusBorg thanks for respond.
I understand that there might be some differences and limitations when wrapping Vuejs component into a WebComponent. Although IMO every framework should strive to minimize those and make DX as fluent as possible.
By only updating docs, the problem won't be solved. Still Vuejs devs w... | 2023-07-11T09:23:23 | 2023-07-11T09:23:23 | {} | NONE |
vuejs | core | 1,630,680,408 | 8,734 | LinusBorg | > When $slots suddenly returning an empty object, that seems to be much worse idea, than returning at least a list of HTML Elements, wouldn't you agree?
I don't really agree. for one, the types would then need to reflect this, and developers would be forced to always take into account the possibilty of a slot sudden... | 2023-07-11T11:49:46 | 2023-07-11T11:49:46 | {} | MEMBER |
vuejs | core | 1,633,656,003 | 7,240 | LinusBorg | > The docs I've read explicitly recommend adding methods for stuff:
The docs you link here still use a plain object (just one with methods on it), not a class, and certainly not a class with private fields | 2023-07-13T06:45:05 | 2023-07-13T06:45:29 | {} | MEMBER |
vuejs | core | 1,617,146,066 | 8,639 | Alfred-Skyblue | TBR | 2023-07-03T02:56:15 | 2023-07-03T02:56:15 | {} | MEMBER |
vuejs | core | 1,617,643,812 | 2,077 | charonchan1991 | I encountered the same issue when trying to implement tabs that share a same component. When a tab is closed by user, I would like to delete the cache of that particular instance only. Here is what I think would be the most elegant way to tackle this in Vue3.
Since KeepAlive takes `include`/`exclude` that accepts co... | 2023-07-03T08:44:11 | 2023-07-03T08:54:56 | {} | NONE |
vuejs | core | 1,619,729,403 | 8,549 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 73cd394f53f863ea46c7efcf4a3a8ca4f0d1260e |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2023-07-04T07:56:36 | 2023-07-04T07:56:36 | {} | NONE |
vuejs | core | 1,620,585,718 | 8,648 | uelquis | yeah, thanks for noticing. I fixed it a couples days ago 😅
| 2023-07-04T17:56:42 | 2023-07-04T17:56:42 | {} | NONE |
vuejs | core | 1,622,770,002 | 8,716 | edison1105 | It is functioning properly. [see](https://play.vuejs.org/#__DEV__eNqNVE1z0zAQ/Ss7zsFhprVDU0rHpGUo9FAO0KHcMAfFXsdqZckjyUlKyH9nJStOykDh4Bnp7cfbfbvWJnrXtsmywyiLZqbQvLVg0HYtCCYXF3lkTR5d5pI3rdIWrjprlYRKqwbiJH2vGh8cv8nlLO3DyZkuFptWMIt0A5iFsJIbNhdYguE/kHI3WPKuySNIyW2WHsTQ1dhHgWAK1WJJSCLUQsHGpauRL2qbwRk2xAvQsrLkcpHBy+RVgFZciOO... | 2023-07-06T01:15:16 | 2023-07-06T01:18:51 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,630,571,511 | 8,753 | Shyam-Chen | Firefox 😵💫 | 2023-07-11T10:27:27 | 2023-07-11T10:27:27 | {} | CONTRIBUTOR |
vuejs | core | 1,632,750,049 | 8,769 | LinusBorg | When you change one of the props, App.vue re-renders. In that re-rendering, you create a fresh array in the template each time and pass that fresh array to prop `a`. Hence why the watcher for the `a` prop gets called each time - its a different array each time. | 2023-07-12T15:25:42 | 2023-07-12T15:25:42 | {} | MEMBER |
vuejs | core | 1,633,045,902 | 8,652 | liamdebeasi | If I understand the migration guide correctly, it sounds like I could be doing `v-model:value` and then emit `update:value`. Unfortunately, that does not address the root problem in https://github.com/vuejs/core/issues/8652#issue-1775279546 where the reference is updated a frame after the `custominput` callback fires.
... | 2023-07-12T18:52:53 | 2023-07-12T18:52:53 | {} | NONE |
vuejs | core | 1,625,599,952 | 8,741 | Shyam-Chen | Duplicate of #8178. | 2023-07-07T15:40:56 | 2023-07-07T15:42:21 | {} | CONTRIBUTOR |
vuejs | core | 1,629,007,135 | 8,522 | solmanter | Hi. I have same issue. I think Vue 3.3.4 does not support right now. And does not work vue-ignore. who have solution? Thanks.
<img width="500" alt="Screenshot 2023-07-10 at 18 43 30" src="https://github.com/vuejs/core/assets/104755033/416dd7c0-5f1d-422f-a4e7-8206a9534b2e">
<img width="500" alt="Screenshot 2023-07-1... | 2023-07-10T13:48:14 | 2023-07-10T13:48:14 | {} | NONE |
vuejs | core | 1,630,010,927 | 8,755 | sixdjango | i know how to write template generic
as:
```vue
<script setup lang="tsx" generic="T extends string | number, U extends {a:string}">
defineProps<{
id: T
list: U[]
}>()
defineSlots<{
default: (props: { item: U }) => VNode
}>()
</script>
``` | 2023-07-11T02:32:50 | 2023-07-11T02:32:50 | {} | NONE |
vuejs | core | 1,632,483,723 | 8,764 | Shyam-Chen | I'm not quite sure what you're trying to convey, but perhaps what you need is `cloneDeep`. | 2023-07-12T12:58:03 | 2023-07-12T12:58:03 | {} | CONTRIBUTOR |
vuejs | core | 1,624,819,554 | 5,836 | MarkSky | > @MarkSky the version of vue in my playground is based on the PR.
I understand now, thank you. | 2023-07-07T06:29:37 | 2023-07-07T06:29:37 | {} | NONE |
vuejs | core | 1,625,111,655 | 8,738 | fEyebrow | yes, you are right. @shengxinjing | 2023-07-07T09:15:25 | 2023-07-07T09:15:25 | {} | NONE |
vuejs | core | 1,628,641,125 | 7,632 | yyx990803 | Hi Thomas, thanks for the PR. We use coverage stats a bit intuitively - i.e. it's primarily used to spot major branches not covered when working on new features. In terms of PRs - to be honest, I don't find coverage stats in PRs to be very meaningful in our case, mostly because our PRs are usually small in scope. I'd r... | 2023-07-10T10:08:36 | 2023-07-10T10:08:36 | {} | MEMBER |
vuejs | core | 1,632,704,396 | 8,760 | Shyam-Chen | @SunnyCrypto You might need to use `nextTick`. I use some charting libraries that redraw charts based on data changes. | 2023-07-12T15:00:23 | 2023-07-12T15:04:37 | {} | CONTRIBUTOR |
vuejs | core | 1,632,898,955 | 8,652 | JessicaSachs | Was the [sync modifier](https://v2.vuejs.org/v2/guide/components-custom-events.html#sync-Modifier ) removed in Vue 3? I can't find docs about it - I'm looking for the raw render fn version of it. | 2023-07-12T17:03:26 | 2023-07-12T17:03:26 | {} | CONTRIBUTOR |
vuejs | core | 1,634,025,061 | 8,743 | dten | I see, so internally it's expecting to be able to use `InstanceType` ? Thanks | 2023-07-13T10:52:03 | 2023-07-13T10:52:17 | {} | NONE |
vuejs | core | 1,617,569,810 | 6,347 | caoguanjie | I also conducted testing and reproduction on my end.
Teleported component brings a serious chain reaction.
Most of the bullet box components in the element plus team use Teleported components
For example, all pop-up components such as Date Picker/Select/Popover/Dialogs/Trailer/Popconfirm/Cascader have memory leakage... | 2023-07-03T07:57:51 | 2023-07-03T07:57:51 | {
"+1": 1
} | NONE |
vuejs | core | 1,618,930,801 | 6,463 | Ingramz | Here is another reproduction that does not seemingly make use of KeepAlive but still triggers this error.
https://stackblitz.com/edit/github-8d62xc
To trigger, click on one of the links.
The code is nonsensical from the practical aspect as it hides the element when it loads the fallback component. Despite this, i... | 2023-07-03T17:38:50 | 2023-07-03T17:41:27 | {} | NONE |
vuejs | core | 1,619,679,593 | 4,776 | qiaohengshan | 怎么修复的 | 2023-07-04T07:34:11 | 2023-07-04T07:34:11 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.