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 | 2,162,874,716 | 11,118 | MineDrum | Ah okay, thats... not what I would've expected, but at least its documented | 2024-06-12T12:23:01 | 2024-06-12T12:23:01 | {} | NONE |
vuejs | core | 2,165,899,431 | 11,125 | alann-sapone | Actually, we migrated from `useVModel` to `defineModel`. But this is the same issue as the one I mentionned before : In our app, it means a huge refacto of our code. As I am not sure that this is the desired behaviour of `defineModel`, I think it's safer to open a ticket to challenge this implementation which changed f... | 2024-06-13T14:49:13 | 2024-06-13T14:49:13 | {
"+1": 1
} | NONE |
vuejs | core | 2,167,086,241 | 11,128 | virtueDe | @jh-Leong bro, thank you for your answer, I'm using a third-party library and I can't modify the state using the returned proxy at the moment | 2024-06-14T02:16:06 | 2024-06-14T02:16:06 | {} | NONE |
vuejs | core | 2,154,128,432 | 9,370 | yyx990803 | The fix is correct, but I refactored the implementation to make it more efficient in 27d9948
- Before: iterating hooks, then for each hook there is searching + splicing
- After: only iterating hooks once | 2024-06-07T05:48:02 | 2024-06-07T05:48:02 | {} | MEMBER |
vuejs | core | 2,156,370,177 | 9,264 | Disservin | I had some additional logic in the first arrow function to build the import path, which I removed when posting here, but yea that is functionally the same anyway | 2024-06-09T07:42:04 | 2024-06-09T07:42:39 | {} | CONTRIBUTOR |
vuejs | core | 2,159,980,676 | 11,109 | linzhe141 | You need to create the correct css url value yourself and bind that in css.
#8117
```vue
<script setup>
const URL_DATA = 'https://images.unsplash.com/photo-1618005182384-a83a8bd57fbe?ixlib=rb-4.0.3&ixid=MnwxMjA3fDB8MHxwaG90by1wYWdlfHx8fGVufDB8fHx8&auto=format&fit=crop&w=1170&q=80'
const url = `url(${URL_DATA})`... | 2024-06-11T07:21:51 | 2024-06-11T07:21:51 | {} | MEMBER |
vuejs | core | 2,162,463,961 | 9,757 | pikax | More tests are always welcomed, the tests look good, but when I merge the #8486 into this branch it still fails
I think this should be merged into #8486 first and then it can be merged with main
| 2024-06-12T08:51:41 | 2024-06-12T08:51:41 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,162,661,847 | 8,306 | Usman024 | > It seems that the
>
> ```
> v-model:is-open="
> isWatchYouTubeEmployerTalkVideoModalOpen
> "
> ```
>
> should be changed to
>
> ```
> v-model:is-open="isWatchYouTubeEmployerTalkVideoModalOpen"
> ```
I was getting error while
npm run build
which were Nuxt Build Error: [vite:define] Transform fa... | 2024-06-12T10:28:45 | 2024-06-12T10:29:28 | {} | NONE |
vuejs | core | 2,167,169,308 | 11,130 | Shyam-Chen | 我認為是預期的，因為你不沒有傳 `attrs` 而是傳 `{}`
你可以改用:
https://vuejs.org/guide/components/attrs.html#fallthrough-attributes
```vue
<template>
<div><slot></slot></div>
</template>
``` | 2024-06-14T04:04:20 | 2024-06-14T04:04:20 | {} | CONTRIBUTOR |
vuejs | core | 2,160,225,071 | 11,109 | haoqunjiang | Expected.
> The var() function cannot be used in property names, selectors or anything else besides property values. (Doing so usually produces invalid syntax, or else a value whose meaning has no connection to the variable.)
https://developer.mozilla.org/en-US/docs/Web/CSS/var
So you can't use it inside a `ur... | 2024-06-11T09:23:47 | 2024-06-11T09:23:47 | {} | MEMBER |
vuejs | core | 2,162,976,950 | 11,117 | aryabawanta | @moritz-baecker-integra based on documentation, the number parsing is not processed if the value cannot be parsed. Check https://vuejs.org/guide/essentials/forms#number (`If the value cannot be parsed with parseFloat(), then the original value is used instead.`).
So on your case, the radio box will not be checked if... | 2024-06-12T13:12:12 | 2024-06-12T13:12:12 | {} | NONE |
vuejs | core | 2,163,000,669 | 11,117 | aryabawanta | The radiobox still gets checked because the value matches the `value` property even in string format (i.e. `Test`), if the value changed into `NaN` as you expected, then the radiobox will not be checked because the `value` property is different than the value (i.e. `Test !== NaN`.
I believed that it is not related ... | 2024-06-12T13:22:44 | 2024-06-12T13:22:44 | {} | NONE |
vuejs | core | 2,164,629,527 | 9,607 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9494856286)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9476964574) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/949... | 2024-06-13T06:38:08 | 2024-06-13T06:38:08 | {} | CONTRIBUTOR |
vuejs | core | 2,154,661,947 | 11,086 | LinusBorg | See my edited comment, misunderstood your problem.
| 2024-06-07T11:39:57 | 2024-06-07T11:39:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,154,984,949 | 11,080 | troppoli | I guess the wrinkle here is that you can't get into this situation with the long hand because props are readlonly. That means you can't even start heading down this path. I'm going to steer clear of defineModel because it looks like a variable but acts like a const asyncly updated variable.
I'm relatively new to vu... | 2024-06-07T14:39:35 | 2024-06-07T14:39:35 | {} | NONE |
vuejs | core | 2,157,141,738 | 11,102 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 91.3 kB | 34.7 kB | 31.3 kB |
| vue.global.prod.js | 148 kB | 54 kB | 48.2 kB |
### Usages
| Name | Size |... | 2024-06-10T03:40:52 | 2024-06-10T03:40:52 | {} | NONE |
vuejs | core | 2,157,492,178 | 7,713 | skirtles-code | A brief summary of how things work currently...
- `v-bind="x"`, where `x` is an object, is expected usage and works fine.
- For falsy values of `x` (e.g. `null`, `undefined`, `false`, `0`, `''`), the `v-bind` is ignored if it is used on an normal element, like a `<div>`. On a `<slot>` it leads to an error being thr... | 2024-06-10T07:01:47 | 2024-06-10T07:01:47 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,159,566,261 | 11,106 | edison1105 | duplicate of https://github.com/vuejs/core/issues/8466 | 2024-06-11T00:50:32 | 2024-06-11T00:50:32 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,164,159,866 | 11,117 | edison1105 | We are tracking this issue in #10886 | 2024-06-13T00:59:26 | 2024-06-13T00:59:26 | {} | MEMBER |
vuejs | core | 2,164,433,890 | 11,121 | edison1105 | @wanghanzhen this one https://github.com/vuejs/core/pull/10397 | 2024-06-13T05:33:50 | 2024-06-13T05:33:50 | {} | MEMBER |
vuejs | core | 2,153,852,205 | 9,264 | yyx990803 | Note that with
```js
const getComponent = () => {
return defineAsyncComponent(() => Promise.resolve(VFoo));
};
```
and
```html
<component :is="getComponent()">
```
**You are defining a new component on every update.** To the parent component, it is rendering a different child component every time.... | 2024-06-07T04:02:37 | 2024-06-07T04:02:37 | {} | MEMBER |
vuejs | core | 2,164,029,342 | 11,117 | aryabawanta | This issue is a duplicate of https://github.com/vuejs/core/issues/10886, theres' a PR to handle `v-model.number` of radio button | 2024-06-12T22:57:22 | 2024-06-12T22:57:22 | {
"heart": 1
} | NONE |
vuejs | core | 2,164,607,431 | 9,607 | Alfred-Skyblue | /ecosystem-ci run | 2024-06-13T06:31:42 | 2024-06-13T06:31:42 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,153,471,705 | 11,076 | Hiws | Probably related to https://github.com/vuejs/core/issues/8144
Workaround can be to use `const props = defineProps({ ... })` and then use `props.config` in the template to get the correct type.
There's also https://github.com/vuejs/language-tools/issues/3820 and https://github.com/vuejs/core/pull/10801 but based o... | 2024-06-06T21:59:19 | 2024-06-06T22:15:55 | {} | NONE |
vuejs | core | 2,154,256,964 | 11,080 | LinusBorg | This is expected behavior. `defineModel()` is a shortcut for receiving a model prop emitting an update event to the parent with the new value.
That new value will only be available after the parent has updated (on the next tick) and sent the new value back down to the child that emitted it. That's the same behaviou... | 2024-06-07T07:29:13 | 2024-06-07T07:29:38 | {} | MEMBER |
vuejs | core | 2,154,403,989 | 11,077 | yyx990803 | This looks like a Vite bug rather than a Vue one - please report to Vite instead. | 2024-06-07T08:59:53 | 2024-06-07T08:59:53 | {} | MEMBER |
vuejs | core | 2,155,889,396 | 11,087 | jh-leong | duplicate of #10547 | 2024-06-08T09:22:10 | 2024-06-08T09:22:10 | {} | MEMBER |
vuejs | core | 2,156,234,736 | 9,336 | skirtles-code | It looks like this may have been fixed by another PR, #10596.
The fixes look fairly different and my TS knowledge isn't good enough to assess the differences between them. Is there any benefit to pursuing the approach in this PR over what's currently on `main`? | 2024-06-09T00:08:43 | 2024-06-09T00:08:43 | {} | CONTRIBUTOR |
vuejs | core | 2,156,945,185 | 11,098 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 91.3 kB | 34.7 kB | 31.3 kB |
| vue.global.prod.js | 148 kB | 54 kB | 48.2 kB |
### Usages
| Name | Size |... | 2024-06-10T00:44:06 | 2024-06-10T00:44:06 | {} | NONE |
vuejs | core | 2,159,569,037 | 11,104 | edison1105 | duplicate of https://github.com/vuejs/core/issues/5256
a workaround https://github.com/vuejs/core/issues/5256#issuecomment-1173891407
fixed via https://github.com/vuejs/core/pull/11067 and will out in v3.5 | 2024-06-11T00:54:02 | 2024-06-11T00:54:02 | {} | MEMBER |
vuejs | core | 2,167,024,637 | 11,128 | virtueDe | ```
<script setup>
import { ref } from 'vue'
class View {
time = 0;
constructor() {
this.setTime()
}
setTime() {
setInterval(() => {
this.time = new Date().getTime()
}, 2000)
}
}
const state = ref(new View())
</script>
<template>
<h1>
state {{ state.time }}</h1>
<... | 2024-06-14T00:57:16 | 2024-06-14T00:59:06 | {} | NONE |
vuejs | core | 2,151,001,416 | 9,403 | skirtles-code | @RodrigoProjects I'm trying to review this change but I'm struggling because of the conflicts. Would you be able to update it to the latest `main` branch? Thanks. | 2024-06-05T21:35:26 | 2024-06-05T21:35:26 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,154,707,823 | 11,086 | LinusBorg | I see. Seems to be related to Suspense. Removing that makes it work. | 2024-06-07T12:10:52 | 2024-06-07T12:10:52 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,160,251,388 | 6,817 | haoqunjiang | Closing as this issue has been fixed in the latest `vue-tsc`. | 2024-06-11T09:32:06 | 2024-06-11T09:32:06 | {} | MEMBER |
vuejs | core | 2,163,007,504 | 11,117 | moritz-baecker-integra | Alright, but the variable "test,value" suddenly has the value "'Test'" a string. Even if its ```Ref<number>``` | 2024-06-12T13:25:55 | 2024-06-12T13:26:20 | {} | NONE |
vuejs | core | 2,165,880,254 | 11,125 | jh-leong | Workaround: use https://vueuse.org/core/useVModel/#usevmodel (see the `shouldEmit` option) | 2024-06-13T14:42:20 | 2024-06-13T14:42:20 | {} | MEMBER |
vuejs | core | 2,165,939,469 | 11,121 | johnsoncodehk | I am unable to focus on this for now, @Doctor-wu are you interested in taking a look at this? | 2024-06-13T15:02:35 | 2024-06-13T15:02:35 | {} | MEMBER |
vuejs | core | 2,167,992,107 | 11,130 | yyx990803 | - Functional components with **explicit props** behaves the same as SFC components (because props declarations are **required** in SFC components)
- Functional component **without** explicit props have different behavior because we can't treat all props as fallthrough.
This is documented and expected behavior. | 2024-06-14T13:02:34 | 2024-06-14T13:02:34 | {} | MEMBER |
vuejs | core | 2,171,976,224 | 11,153 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 91.5 kB | 34.7 kB | 31.3 kB |
| vue.global.prod.js | 149 kB | 54 kB | 48.3 kB |
### Usages
| Name | Size |... | 2024-06-17T00:49:56 | 2024-06-17T00:49:56 | {} | NONE |
vuejs | core | 2,177,433,840 | 11,136 | yangliguo7 | loader 函数的执行是一个异步执行 ，被 errorHandler 捕获
https://github.com/vuejs/core/blob/main/packages/runtime-core/src/apiAsyncComponent.ts#L184-L197
或者父组件捕获子组件异常
https://play.vuejs.org/#eNqlVcFu00AQ/ZWRhVQnsmzacjJJRKkqAUKAgN4s0cXeJNvau9buOk0U5YK4grjwGVyhUvkcCnwGs7u2E0dtVQnlYHtmdubNmzebpXdQluGsol7sDTQtypxoOkr44FAU5WgQ2Qd+Rh... | 2024-06-19T02:42:35 | 2024-06-19T02:50:12 | {} | CONTRIBUTOR |
vuejs | core | 2,180,044,323 | 11,177 | LinusBorg | I don't understand that explanation given what I demonstrated in the playground, because it would look like this:
1. vue pass object as attribute value to the custom web element.
2. browser converts object to string
3. ext component stores attr value in the property, if type of value is object, which it is not, beca... | 2024-06-20T07:53:08 | 2024-06-20T07:53:58 | {} | MEMBER |
vuejs | core | 2,180,130,953 | 11,125 | alann-sapone | @yangxiuxiu1115 : Hey there !
Thank you for your pull request opening :). Just wondering : Did you fix it because it wasn't the desired behavior ? | 2024-06-20T08:37:04 | 2024-06-20T08:37:04 | {} | NONE |
vuejs | core | 2,167,308,135 | 11,134 | linzhe141 | After fixing the code, the compiled result of the local-dev playground is still `test:{type:Object}`. Maybe this is a bug in vue-repl
| 2024-06-14T06:26:13 | 2024-06-14T06:46:31 | {} | MEMBER |
vuejs | core | 2,169,282,565 | 11,143 | gkweb | @modos Doesn't this fall into the existing warning in the docs regarding breaking of synchronisation between parent / child when no value supplied to child?
_Quote from docs:_
https://vuejs.org/api/sfc-script-setup.html#definemodel
> If you have a default value for defineModel prop and you don't provide any va... | 2024-06-15T10:32:39 | 2024-06-15T10:32:39 | {} | NONE |
vuejs | core | 2,170,945,581 | 11,147 | skirtles-code | Maybe the same as #10806? | 2024-06-15T22:22:49 | 2024-06-15T22:22:49 | {} | CONTRIBUTOR |
vuejs | core | 2,171,361,940 | 11,147 | adamsol | Right, duplicate. | 2024-06-16T09:46:25 | 2024-06-16T09:46:25 | {} | NONE |
vuejs | core | 2,171,975,953 | 11,152 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 91.5 kB | 34.7 kB | 31.3 kB |
| vue.global.prod.js | 149 kB | 54 kB | 48.3 kB |
### Usages
| Name | Size |... | 2024-06-17T00:49:27 | 2024-06-17T00:49:27 | {} | NONE |
vuejs | core | 2,172,115,329 | 11,157 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 91.5 kB | 34.7 kB | 31.3 kB |
| vue.global.prod.js | 149 kB | 54 kB | 48.3 kB |
### Usages
| Name | Size |... | 2024-06-17T03:38:54 | 2024-06-17T03:38:54 | {} | NONE |
vuejs | core | 2,175,482,105 | 11,078 | yangliguo7 | > Vue SFC Playground
u use ssr option
| 2024-06-18T08:13:13 | 2024-06-18T08:13:13 | {} | CONTRIBUTOR |
vuejs | core | 2,175,500,931 | 11,166 | yangliguo7 | ```
<script setup lang="ts">
import { onMounted, ref } from 'vue'
const compRef = ref<{x:1}>(undefined)
onMounted(() => {
console.log(compRef.value.x) // 你认为这里应该报错吗？
})
</script>
<template>
<h1>123{{ compRef }}</h1>
</template>
``` | 2024-06-18T08:21:48 | 2024-06-18T08:21:48 | {} | CONTRIBUTOR |
vuejs | core | 2,179,775,878 | 11,177 | jh-leong | Invalid reproduction, could you please provide an actual reproduction? | 2024-06-20T04:18:58 | 2024-06-20T04:18:58 | {} | MEMBER |
vuejs | core | 2,179,784,262 | 11,177 | jh-leong | Are you using custom elements with `value`, `checked`, or `selected` props? This might be a duplicate of issue #11163. | 2024-06-20T04:31:08 | 2024-06-20T04:50:26 | {} | MEMBER |
vuejs | core | 2,179,939,432 | 11,177 | LinusBorg | > Should I create and deploy reproduction code? I think the problem is clear.
The problem is not really clear. Because the line you point to can't really be the problem on its own, here's why:
HTML *Attributes* are **always** converted to strings. That's part of the spec, and you can see a demo of this behaviour ... | 2024-06-20T06:46:44 | 2024-06-20T07:36:37 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,180,257,531 | 11,182 | LinusBorg | I think this patch is worthwhile, but I want to mention that this is an edge case for specific web component implementations, and the `typeof` *might* add a (small, likely neglectable) perf overhead when patching a lot of attributes. | 2024-06-20T09:42:48 | 2024-06-20T09:42:48 | {} | MEMBER |
vuejs | core | 2,167,850,475 | 3,795 | jods4 | 3 years later, I have deployed several large apps in production that wrap multi-root components with Suspense and never had any issue.
As of writing, Vue v.3.4.27 still emits this warning.
Could the warning be removed?
BTW Suspense was a key new feature of Vue 3.0, but it's still experimental today.
On which aspe... | 2024-06-14T11:46:16 | 2024-06-14T11:46:16 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 2,168,310,426 | 11,123 | yyx990803 | The resolution has some bugs that are resolved in a476692ed, but it does not completely fix the usage.
Note that by including `FormHTMLAttributes` you are going to declare **hundreds** of props and the runtime declaration will be very large - this is probably not what you want, I assume you only want the component t... | 2024-06-14T15:50:40 | 2024-06-14T15:50:40 | {} | MEMBER |
vuejs | core | 2,172,151,071 | 11,136 | 1340145680 | > Invalid reproduction - this involves your build setup so a playground link is insufficient to debug the issue. Please provide an actual reproduction.无效的复制 - 这涉及您的构建设置，因此游乐场链接不足以调试问题。请提供真实的复制品。
new SFC Playground URL [Link](https://play.vuejs.org/#eNqlVNtu1DAQ/ZWRhdRsFcXl8hS2FQVVAoQAAX2zRE3i3XXr2JHt7EWr/XfGTpy9qMsL... | 2024-06-17T04:00:56 | 2024-06-17T04:00:56 | {} | NONE |
vuejs | core | 2,172,912,199 | 8,482 | vkrepkiy | I tried to re-use vuetify component's props `type FormInputProps = VTextField['$props']` and as under the hood Vuetify exports via `InstanceType<typeof VTextField>`, also ended up with error `[@vue/compiler-sfc] Unresolvable type reference or unsupported built-in utility type`
version 3.4.29 | 2024-06-17T09:46:17 | 2024-06-17T09:46:17 | {
"+1": 3
} | NONE |
vuejs | core | 2,174,633,731 | 11,143 | sanba-anass | there you go lol
```vue
<script setup>
import { ref } from 'vue';
const count = defineModel({default: ref([])});
</script>
<template>
{{ count}}
<button @click="count.value.push(1);">Count</button>
</template>
```
| 2024-06-17T23:44:06 | 2024-06-17T23:45:05 | {} | NONE |
vuejs | core | 2,174,986,186 | 11,163 | yangxiuxiu1115 | 537a571 | 2024-06-18T04:39:19 | 2024-06-18T04:39:19 | {} | CONTRIBUTOR |
vuejs | core | 2,176,341,729 | 9,121 | DrJume | This would be nice to have 👍 | 2024-06-18T15:08:15 | 2024-06-18T15:08:15 | {} | CONTRIBUTOR |
vuejs | core | 2,180,038,464 | 11,177 | zdm | 1. vue pass object as attribute value to the custom web element.
2. ext component stores attr value in the property, if type of value is `object`. | 2024-06-20T07:49:44 | 2024-06-20T07:49:44 | {} | NONE |
vuejs | core | 2,180,131,493 | 11,170 | Doctor-wu | > @Doctor-wu Finally got the reproduction. Here is the link: [play.vuejs.org/#eNp9UstOwzAQ/JWVL7SiSoFyoaSVAIEEB6iAoyWUJpuSktiWH6Eoyr+zdvpCoj0l2ZnZnd1Mw26UimqHbMxik+pCWTBonZpyUVRKagsNpLJSzmI2AI05tJBrWcEJiU644CKVwljIpYSJx3tn/etdeZ5oKm8a9Hp9mEyh4QK8IKqT0iGcTuCcJEBq67TYIVRs95ulB1qtdQ1kYz9w3bbdyeNhtxotFVusVJlYpHeAOCvqaUMbRh... | 2024-06-20T08:37:22 | 2024-06-20T09:03:37 | {} | MEMBER |
vuejs | core | 2,180,246,276 | 11,183 | Doctor-wu | /ecosystem-ci run | 2024-06-20T09:36:45 | 2024-06-20T09:36:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,183,078,870 | 11,160 | skirtles-code | There hasn't been an [RFC](https://github.com/vuejs/rfcs) for this change. While I understand that it is a relatively small change, I do worry that we may miss out on feedback from the community without an RFC.
I read through the original RFC for `v-bind` in `<style>`. The use case described here doesn't seem to be ... | 2024-06-21T16:36:57 | 2024-06-21T16:36:57 | {} | CONTRIBUTOR |
vuejs | core | 2,183,649,129 | 9,232 | edison1105 | /ecosystem-ci run | 2024-06-22T01:23:47 | 2024-06-22T01:23:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,167,797,870 | 11,126 | jleifeld | Thanks Evan for fixing the root cause! 👍 | 2024-06-14T11:10:36 | 2024-06-14T11:10:36 | {} | NONE |
vuejs | core | 2,171,036,384 | 11,149 | ruisnowy | 
| 2024-06-16T04:04:36 | 2024-06-16T04:04:36 | {} | NONE |
vuejs | core | 2,176,113,655 | 11,071 | thomasaull | @jh-leong Yeah no, I want to use the generic to set a type for a component which wraps an `<input/>` element, [here's an example](https://play.vuejs.org/#eNqVVeFu2zYQfpWb/kgGUgnZhg3T7LRra2Ad1q5Yvf2JglWWTzZjiRRIykmWGujT9MH6JL07SbbSFCn6R+KRx4/f3X083ga/NU28azFIg6krrGo8OPRtA1Wu17Ms8C4LzjKt6sZYDy9vXuim9VBaU0MYJ73NAOGvmc502e... | 2024-06-18T13:32:04 | 2024-06-18T13:32:16 | {} | NONE |
vuejs | core | 2,178,885,994 | 11,170 | Doctor-wu | @wanghanzhen could you try to provide reproduce, I think it's necessary to add `resetTracking` here to align behaviour with others dirty level | 2024-06-19T14:42:53 | 2024-06-19T14:42:53 | {} | MEMBER |
vuejs | core | 2,179,864,853 | 8,338 | Alfred-Skyblue | /ecosystem-ci run | 2024-06-20T05:46:05 | 2024-06-20T05:46:05 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,180,049,864 | 11,177 | zdm | 1. you pass object as attr value.
2. extjs has handler for set attribute value operation, it called before browser. If value is object - extjs stores it in property instead of attribute. | 2024-06-20T07:56:23 | 2024-06-20T07:56:23 | {} | NONE |
vuejs | core | 2,169,198,410 | 5,912 | beskar-developer | @johnsoncodehk
Hi. I have a scenario that has a different outcome in different versions of vue!
```
<template>
{{ items }}
</template>
<script setup>
import { computed, reactive, watch } from "vue";
const someArray = [Math.random(), Math.random(), Math.random()];
const someReactive = reactive({... | 2024-06-15T08:10:42 | 2024-06-15T08:10:42 | {} | NONE |
vuejs | core | 2,171,038,807 | 11,149 | jh-leong | This is expected behavior.
In your example, `name` is not a `ref`, which means the view will not reactively update when `name` changes. Since you use `name` in the `template`, it retrieves the value of `name` when the view updates (triggered by `changePerson`). By this time, `name` has already changed.
BTW, next ... | 2024-06-16T04:15:23 | 2024-06-16T04:15:23 | {} | MEMBER |
vuejs | core | 2,171,625,246 | 11,023 | Rusinas | Is there a chance to merge it soon? 👉👈 | 2024-06-16T13:22:50 | 2024-06-16T13:22:50 | {
"confused": 1,
"eyes": 2
} | NONE |
vuejs | core | 2,172,651,802 | 11,146 | FireBushtree | > Should this also be added to https://github.com/vuejs/core/blob/main/packages/runtime-core/src/index.ts#L63?
i will do, thx | 2024-06-17T08:30:12 | 2024-06-17T08:30:12 | {} | NONE |
vuejs | core | 2,173,390,531 | 11,143 | LinusBorg | This is not really related to `defineModel` at all, and it's expected behavior. You provided a nonreactive array as the default value for the `defineModel()` ( = the `modelValue` prop that it will create)
That means you are now mutating a plain, non-reactive array. So no reactive effects are being triggered.
The ... | 2024-06-17T13:24:09 | 2024-06-17T13:24:54 | {} | MEMBER |
vuejs | core | 2,179,790,768 | 11,177 | zdm | Should I create and deploy reproduction code?
I think the problem is clear. | 2024-06-20T04:39:19 | 2024-06-20T04:39:19 | {} | NONE |
vuejs | core | 2,168,231,740 | 11,121 | johnsoncodehk | The reproducible case can be simplified to the following code (without using computed), I think causing infinite recursion is expected behavior.
```html
<script setup>
import { ref } from 'vue'
const foo = ref(0);
const bar = () => {
foo.value += 1;
return foo.value;
};
</script>
<template>
<div>... | 2024-06-14T15:03:48 | 2024-06-14T15:04:08 | {} | MEMBER |
vuejs | core | 2,169,209,860 | 5,912 | skirtles-code | @beskar-developer. This PR was merged a long time ago. If you think you've found a bug then it'd be better to open a new issue at https://github.com/vuejs/core/issues. If you're unsure whether it's a bug you could also discuss it at either https://github.com/vuejs/core/discussions or on [Discord](https://chat.vuejs.org... | 2024-06-15T08:34:27 | 2024-06-15T08:34:27 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 2,177,911,812 | 5,481 | haoqunjiang | It works fine after updating all the dependencies to the latest versions. So, I consider this issue resolved.
If you still encounter similar problems, please open a new issue with new reproductions. | 2024-06-19T07:08:08 | 2024-06-19T07:08:08 | {} | MEMBER |
vuejs | core | 2,180,028,120 | 11,177 | zdm | Yes. the code, you posted above, will work. | 2024-06-20T07:43:33 | 2024-06-20T07:43:33 | {} | NONE |
vuejs | core | 2,181,018,158 | 8,482 | Trandx | 🙏 thanks
Le jeu. 20 juin 2024 à 15:14, rcomesan ***@***.***> a écrit :
> I'm also getting the same error when trying to import an inferred zod type
> [plugin:vite:vue] ***@***.***/compiler-sfc] Unresolvable type reference or
> unsupported built-in utility type
>
> import { z } from 'zod';
> export const Ema... | 2024-06-20T15:45:48 | 2024-06-20T15:45:48 | {} | NONE |
vuejs | core | 2,181,868,518 | 10,948 | lejunyang | I think we could have a `formAssociated` option in `defineCustomElement`, and add that static prop in `VueCustomElement`
```js
static formAssociated = !!Comp.formAssociated
```
`ElementInternals` should be attached if we want to make it associate with form.
`ElementInternals` can also be used to access [Accessibil... | 2024-06-21T02:33:44 | 2024-06-21T09:31:17 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,183,665,113 | 9,232 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9621777493)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9608518200) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-06-22T01:30:36 | 2024-06-22T01:30:36 | {} | CONTRIBUTOR |
vuejs | core | 2,167,586,454 | 11,126 | yyx990803 | Thanks for the PR. After looking at this, the logic in `softAssertCompatEnabled` works as intended - it's just it was incorrectly used in the case for the checks of `ATTR_FALSE_VALUE`.
I've fixed the root cause in 04729ba21 and reused the test from this PR. | 2024-06-14T09:04:13 | 2024-06-14T09:04:13 | {
"heart": 2
} | MEMBER |
vuejs | core | 2,169,688,262 | 5,912 | basvanmeurs | > @johnsoncodehk Hi. I have a scenario that has a different outcome in different versions of vue!
>
> ```
> <template>
> {{ items }}
> </template>
>
> <script setup>
> import { computed, reactive, watch } from "vue";
>
> const someArray = [Math.random(), Math.random(), Math.random()];
>
> const ... | 2024-06-15T13:52:35 | 2024-06-15T13:52:35 | {} | CONTRIBUTOR |
vuejs | core | 2,175,864,887 | 11,167 | thomasaull | @jh-leong Thanks, I searched for similar issues but could not find the one you linked… | 2024-06-18T11:25:17 | 2024-06-18T11:25:26 | {} | NONE |
vuejs | core | 2,180,017,545 | 11,170 | wanghanzhen | @Doctor-wu Finally got the reproduction. Here is the link:
https://play.vuejs.org/#eNp9UstOwzAQ/JWVL7SiSoFyoaSVAIEEB6iAoyWUJpuSktiWH6Eoyr+zdvpCoj0l2ZnZnd1Mw26UimqHbMxik+pCWTBonZpyUVRKagsNpLJSzmI2AI05tJBrWcEJiU644CKVwljIpYSJx3tn/etdeZ5oKm8a9Hp9mEyh4QK8IKqT0iGcTuCcJEBq67TYIVRs95ulB1qtdQ1kYz9w3bbdyeNhtxotFVusVJlYpHeAOCvq... | 2024-06-20T07:37:07 | 2024-06-20T07:37:07 | {
"+1": 1
} | NONE |
vuejs | core | 2,180,025,023 | 11,177 | zdm | The problem is that `store` is the instance of the class, it is not a plain object, and can't be stringified / parsed from json.
I think your bugfix is not correct, you should not modify attrs values, or strictly limit the scope, where you do this.
If you need to convert Symbols to strings in some specific cases - ... | 2024-06-20T07:41:35 | 2024-06-20T07:41:35 | {} | NONE |
vuejs | core | 2,180,052,419 | 11,177 | LinusBorg | Ah, I see, thanks. So it overrides the default implementation `setAttribute`. that's an .... interesting approach. | 2024-06-20T07:57:52 | 2024-06-20T07:57:52 | {} | MEMBER |
vuejs | core | 2,180,253,090 | 11,170 | Doctor-wu | @wanghanzhen Submitted #11183 for fixing both #11169 and #11181, reused your test case | 2024-06-20T09:40:27 | 2024-06-20T09:40:47 | {} | MEMBER |
vuejs | core | 2,180,626,833 | 11,183 | wanghanzhen | Excellent job! I tried it and it works fine in my project. | 2024-06-20T13:01:30 | 2024-06-20T13:01:30 | {
"rocket": 1
} | NONE |
vuejs | core | 2,183,544,373 | 10,537 | skirtles-code | I think we may need to make a distinction between properties and attributes here.
The original issue was specifically about properties, not attributes. I think having default prop values reflected in the properties of the element make sense, but I'm not so sure about the attributes.
I've had a look through some r... | 2024-06-21T22:31:54 | 2024-06-21T22:31:54 | {} | CONTRIBUTOR |
vuejs | core | 2,167,656,699 | 11,133 | TheAlexLichter | This might also be "confused" with the [VueUse implementation](https://vueuse.org/shared/toRef/#usage) which allows passing raw values in which are then converted into a ref.
I wonder if it'd make sense to replicate such behavior 🤔 | 2024-06-14T09:43:17 | 2024-06-14T09:43:17 | {} | NONE |
vuejs | core | 2,167,740,210 | 11,135 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9514629335)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9510878921) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-06-14T10:33:30 | 2024-06-14T10:33:30 | {} | CONTRIBUTOR |
vuejs | core | 2,168,116,065 | 9,270 | thany | This is not fixed in the latest update (3.4.28).
For me this error only doesn't occur if I place some hardcoded text into a teleport, like so:
```
<Teleport to="#foo">
blah
</Teleport>
```
While this doesn't produce the error, it does produce a warning:
```
Failed to locate Teleport target with selec... | 2024-06-14T14:00:03 | 2024-06-14T14:00:03 | {} | NONE |
vuejs | core | 2,178,026,811 | 11,071 | jh-leong | @thomasaull [try this](https://play.vuejs.org/#eNqdVE1vm0AQ/StTLmDJsg+5Udtp01hqqiaNWquXkAPFg0MCu2h3sZ0m/u+dmTWYfDSVegF2Pt6+mXnMQ/CxrkfrBoM4mNjMFLUDi66poUzVapoEzibBLFFFVWvj4Pz+TNWNg9zoCsLR+JOuJDt8n6hE5Y3KXKEVaHWaOpTQaElfMfB5AA+JAsi0srrEUalXUdiLDIfAsYNE7RI1GXsydDUdHFZ1ST46AUxaEu6+RmLISUkAHwo20rkHSeZ4nZYNhyncCItokATjV4HQG... | 2024-06-19T08:03:14 | 2024-06-19T08:03:14 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,179,638,599 | 11,166 | Alfred-Skyblue | ts类型不会影响运行时结果 | 2024-06-20T01:04:13 | 2024-06-20T01:04:13 | {} | MEMBER |
vuejs | core | 2,180,029,660 | 11,177 | LinusBorg | > The problem is that store is the instance of the class, it is not a plain object, and can't be stringified / parsed from json.
But that's the part I don't understand. I just demonstrated to you that attributes will *always* be stringified by the browser. So ExtJS *must* re-parse a string into a Store Class instanc... | 2024-06-20T07:44:29 | 2024-06-20T07:44:59 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.