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,517,323,833 | 8,131 | yyx990803 | Is this a regression only in 3.3 alpha, or reproducible in 3.2? | 2023-04-21T06:20:03 | 2023-04-21T06:20:03 | {} | MEMBER |
vuejs | core | 1,517,627,069 | 8,133 | LinusBorg | This is expected and documented.
<img width="753" alt="Bildschirmfoto 2023-04-21 um 12 33 29" src="https://user-images.githubusercontent.com/1444526/233614963-de5b560c-3c2a-4afb-bdca-bfe6cb098db7.png">
While you don't use `await`, `setTimeout` callbacks are still *asynchronous*. | 2023-04-21T10:34:17 | 2023-04-21T10:34:17 | {} | MEMBER |
vuejs | core | 1,519,008,397 | 8,140 | sqal | It seems that it does not work because you're using project references. If you add `paths` in your `tsconfig.json` it will work:
```json
{
"compilerOptions": {
"paths": {
"@/*": ["./src/*"]
}
},
"files": [],
"references": [
{
"path": "./tsconfig.node.json"
},
{
... | 2023-04-23T09:22:29 | 2023-04-23T09:22:29 | {} | CONTRIBUTOR |
vuejs | core | 1,519,733,776 | 8,146 | shiwanjun1995 | @https://github.com/posva | 2023-04-24T09:34:59 | 2023-04-24T09:34:59 | {} | NONE |
vuejs | core | 1,521,389,213 | 661 | jakearchibald | Should this be reconsidered now the browser support of `inert` is much-improved (86.73%), as it's now supported in all engines?
Yes, it's really easy to add this yourself, but I'm not sure many developers will realise they _should_ do this in almost all cases.
Adding an opt-in to this behaviour on `<Transition>` ... | 2023-04-25T08:30:14 | 2023-04-25T08:30:14 | {} | NONE |
vuejs | core | 1,522,075,785 | 8,152 | wht300 | I am currently unclear if there is a way to achieve your requirements,
but based on my current understanding of Vue's capabilities, I can currently think of the following ways:
1. Give up the validator and downgrade to what [Shyam-Chen](https://github.com/Shyam-Chen) mentioned
```
interface Props {
propF?: '... | 2023-04-25T16:20:23 | 2023-04-25T16:20:23 | {
"+1": 3
} | NONE |
vuejs | core | 1,522,762,798 | 7,184 | jakubhruby | Could anyone merge this, please? | 2023-04-26T04:27:19 | 2023-04-26T04:27:19 | {
"+1": 2
} | NONE |
vuejs | core | 1,515,861,433 | 8,117 | pangao66 | v-bind css 功能里面是可以写表达式的， 当你写backgroud-image的 时候是需要你自己添加 url（） 函数
When using the 'v-bind css' function, expressions can be added. When using the 'background-image' property, it is necessary to manually add the 'url()' function.
```vue
<script setup>
import testjPG from './test.jpeg'
const bgUrl = 'https://pcm-301... | 2023-04-20T07:36:01 | 2023-04-20T10:45:28 | {
"+1": 19,
"confused": 1,
"rocket": 5
} | NONE |
vuejs | core | 1,517,628,108 | 8,131 | LinusBorg | The playground example also breaks with 3.2.47 selected | 2023-04-21T10:35:18 | 2023-04-21T10:35:18 | {} | MEMBER |
vuejs | core | 1,521,035,442 | 8,144 | yyx990803 | FYI the fix proposed [here](https://github.com/vuejs/language-tools/issues/2192#issuecomment-1518672899) doesn't pass the dts tests in core. | 2023-04-25T01:35:29 | 2023-04-25T01:35:29 | {} | MEMBER |
vuejs | core | 1,521,557,899 | 8,153 | Shyam-Chen | ```ts
watchEffect(() => {
console.log(countOnSlot.value, countOnDiv.value);
});
``` | 2023-04-25T10:34:02 | 2023-04-25T10:34:02 | {} | CONTRIBUTOR |
vuejs | core | 1,521,672,308 | 8,152 | edison1105 | `defineProps()` is actually a Composition API.
I don't understand what you mean.
| 2023-04-25T12:03:08 | 2023-04-25T12:03:08 | {} | MEMBER |
vuejs | core | 1,523,456,683 | 5,272 | jd-solanki | @yyx990803 I heavily use `ExtractPropTypes` in my UI lib and later found that I'm facing the similar issue as mentioned.
As we are already working on type improvements for vue 3.3, adding `ExtractExternalPropTypes` or something similar will make props & it's type reusability much more ease.
Here's how I reuse pr... | 2023-04-26T13:49:02 | 2023-04-26T13:49:35 | {} | NONE |
vuejs | core | 1,524,419,266 | 8,168 | modelair | did u mean this?
```ts
interface MyProps extends MyOtherProps {
color?: MyColor
modelValue?: number
}
const props = withDefaults(defineProps<MyProps>(), {
color: 'green',
modelValue: 0
})
```
| 2023-04-27T01:45:30 | 2023-04-27T01:46:29 | {} | NONE |
vuejs | core | 1,524,433,379 | 8,168 | jd-solanki | Thanks for your response.
No! It's already in docs.
I'm saying, Generating type from object syntax as shared in the code snippet. | 2023-04-27T01:53:25 | 2023-04-27T01:53:25 | {} | NONE |
vuejs | core | 1,515,926,443 | 8,083 | edison1105 | > > @Hccake Would you mind providing a runnable minimal reproduction?
>
> @edison1105 Ok, the link is here: [codesandbox.io/p/github/Hccake/vue3-typescript/master](https://codesandbox.io/p/github/Hccake/vue3-typescript/master)
>
> If you use vue 3.2.x version code can run normally
```typescript
import type {B... | 2023-04-20T08:24:12 | 2023-04-20T08:45:41 | {} | MEMBER |
vuejs | core | 1,518,959,771 | 4,034 | terwer | Thanks [Trinovantes](https://github.com/Trinovantes) , helps me a lot | 2023-04-23T06:17:43 | 2023-04-23T06:17:54 | {} | NONE |
vuejs | core | 1,521,643,817 | 6,926 | edison1105 | @Lyokolux
It can work normally because this code will run after mounting.
```js
(_ctx) => ({
"1c89043a-color": _unref(color)
})
```
it works fine see [demo](https://play.vuejs.org/#__DEV__eNpNj8HKwjAQhF9lyaUV/C1e/VPBV/CcS01WG0iTkGwLUvrubtoi5pQdZr6dncUtxtM0orgISThE1xFelQd+0tgJtOtybpXoz0rsOkBvy082bGBNNj9BHrNONhJ... | 2023-04-25T11:40:23 | 2023-04-25T11:40:23 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,522,682,429 | 8,156 | zhuyuanmin | This result： -45258083-pTop: NaN; | 2023-04-26T02:36:39 | 2023-04-26T02:36:39 | {} | NONE |
vuejs | core | 1,522,990,852 | 7,437 | 7Z0nE | @smallnine9 @sxzz Why was this PR closed without comment? I think this is a much needed feature and should be merged soon. | 2023-04-26T08:24:04 | 2023-04-26T08:24:04 | {
"+1": 2
} | NONE |
vuejs | core | 1,518,546,579 | 7,886 | sapphi-red | This is a problem on plugin-vue side: https://github.com/vitejs/vite-plugin-vue/issues/130
This issue can be closed.
| 2023-04-22T07:29:24 | 2023-04-22T07:29:24 | {} | CONTRIBUTOR |
vuejs | core | 1,519,409,774 | 6,435 | edison1105 | see #6553 and https://github.com/vuejs/core/issues/6553#issuecomment-1232468857 | 2023-04-24T05:33:00 | 2023-04-24T05:33:00 | {} | MEMBER |
vuejs | core | 1,522,029,902 | 8,152 | wht300 | It seems that this problem can be described as:
• Problem premise: The document describes:
> defineProps or defineEmits can only use either runtime declaration OR type declaration. Using both at the same time will result in a compile error
• Requirement: The user expects to use defineProps with a type declarati... | 2023-04-25T15:47:53 | 2023-04-25T15:47:53 | {
"+1": 1
} | NONE |
vuejs | core | 1,522,754,460 | 8,153 | Shyam-Chen | ```ts
watch(
refs,
async () => {
await nextTick();
console.log([...refs.value]);
},
{
deep: true,
flush: 'post',
},
);
// or
watch(
refs,
() => {
nextTick(() => {
console.log([...refs.value]);
});
},
{
deep: true,
flush: 'post',
},
);... | 2023-04-26T04:15:10 | 2023-04-26T04:16:58 | {} | CONTRIBUTOR |
vuejs | core | 1,523,868,960 | 8,164 | sqal | There was some breaking changes introduced in alpha.10 [6b13e04](https://github.com/vuejs/core/commit/6b13e04b4c83fcdbb180dc1d59f536a1309c2960#diff-c557d6f1af62f63358d9628e8b653101b9ac1c391e3ac124a44bb69826b2574cR29) in relation to previous alpha releases, with the addition of `options.propsDestructure` check.
Since... | 2023-04-26T18:29:24 | 2023-04-26T18:33:22 | {} | CONTRIBUTOR |
vuejs | core | 1,525,716,364 | 4,662 | shareefhadid | Not sure why after this many comments, and all this time, this still gets no attention from the Vue team 😞. A simple update or reason as to why this has not been implemented would be sufficient. | 2023-04-27T13:40:26 | 2023-04-27T13:40:26 | {
"+1": 24,
"heart": 6
} | NONE |
vuejs | core | 1,515,793,241 | 8,083 | Hccake | > @Hccake Would you mind providing a runnable minimal reproduction?
@edison1105 Ok, the link is here: https://codesandbox.io/p/github/Hccake/vue3-typescript/master
If you use vue 3.2.x version code can run normally | 2023-04-20T06:42:50 | 2023-04-20T06:42:50 | {} | NONE |
vuejs | core | 1,516,034,821 | 8,104 | pangao66 | element-plus 中inputProps为运行时props,InputProps为ts类型props， 但是源码是用了一个build函数
const inputProps = buildProps({
id: {
type: String,
default: void 0
},
)}
导致不能正确推导
import { inputProps} from "element-plus";
defineProps(inputProps);
看样子是webstorm的问题， vscode可以正确推导
尤大能否联系 webstorm相关团队， webstorm InstanceT... | 2023-04-20T09:45:24 | 2023-04-20T09:51:50 | {} | NONE |
vuejs | core | 1,518,964,576 | 4,294 | Miofly | can not get OtherProps
```ts
type OtherProps = Pick<InputProps, 'suffixIcon' | 'prefixIcon' | 'clearIcon'>
export interface SearchProps extends OtherProps {
modelValue?: string | number;
placeholder?: string;
clearable?: boolean;
width?: string | number;
popoverCfg?: PopoverProps;
visible: boolea... | 2023-04-23T06:39:22 | 2023-04-23T06:39:38 | {} | NONE |
vuejs | core | 1,522,986,817 | 7,447 | 7Z0nE | @smallnine9 Why was this closed? This PR is much needed. | 2023-04-26T08:20:54 | 2023-04-26T08:24:28 | {} | NONE |
vuejs | core | 1,523,252,006 | 5,844 | maximilliangeorge | There's a PR up that claims to fix this issue.
https://github.com/vuejs/core/pull/5952
However, it's been pretty stale for months now. Hope to see it merged soon. | 2023-04-26T11:21:46 | 2023-04-26T11:21:46 | {
"+1": 15
} | NONE |
vuejs | core | 1,515,910,519 | 8,104 | pangao66 | @yyx990803 主要是想为了编辑器能够很好的提示， 我有个建议能否 类型和运行时同时存在呢，
```vue
<script setup lang="ts">
import { ElInput } from 'element-plus'
import type { InputProps } from 'element-plus'
import MyComponent from '@/components/my-component.vue'
defineProps<Partial<InputProps>>(ElInput.props)
// 或者任意自定义组件，未暴露props类型的
defineProps<I... | 2023-04-20T08:12:20 | 2023-04-20T08:22:14 | {} | NONE |
vuejs | core | 1,517,933,851 | 5,540 | rdsteiner | Are there any plans on adding this new feature? The PR from @LinusBorg is getting pretty old. | 2023-04-21T14:36:51 | 2023-04-21T14:36:51 | {} | NONE |
vuejs | core | 1,521,055,325 | 8,147 | wht300 | > I don't think you should use `refs.length`,but rather use `list.length`.`refs.length` and `refs.set` will loop until the maximum number of updates are reached.
In the real scenario, the `v-for` is a custom component.
For example, if you need to iterate through the refs when you submit, and you need to loop through ... | 2023-04-25T02:08:45 | 2023-04-25T02:15:56 | {} | NONE |
vuejs | core | 1,521,386,683 | 6,926 | Lyokolux | FYI this bug is currently happening in vue 3.2.47. I am simply running the `vite --host` command.
Given the shortened following component:
```html
<template>
<Icon :icon="icon" />
</template>
<script setup lang="ts">
import { computed, toRefs } from 'vue'
const props = defineProps<{
state: 'pendi... | 2023-04-25T08:28:23 | 2023-04-25T08:28:23 | {} | NONE |
vuejs | core | 1,522,728,510 | 8,153 | wht300 | > This is by design.
>
> when only the slot depends on a reactive value, then only the child component consuming the slot actually needs to re-render, not the parent. This has significant perfomance advantages. The logical consequence is that in such scenarios, `beforeUpdate` and `updated` hooks in the parent are no... | 2023-04-26T03:37:58 | 2023-04-26T03:38:57 | {} | NONE |
vuejs | core | 1,525,958,872 | 8,169 | dbrath-impacs | Just FYI for anyone else interested in this functionality, there is a composable in VueUse that does the same thing - [computedWithControl](https://vueuse.org/shared/computedWithControl/).
Example from the docs:
```typescript
import { computedWithControl } from '@vueuse/core'
const source = ref('foo')
const co... | 2023-04-27T16:04:34 | 2023-04-27T16:04:34 | {} | NONE |
vuejs | core | 1,564,624,238 | 8,413 | yyx990803 | It's expected behavior as explained by @baiwusanyu-c | 2023-05-26T16:15:29 | 2023-05-26T16:15:29 | {} | MEMBER |
vuejs | core | 1,565,319,689 | 1,366 | jd-solanki | @LinusBorg I guess we can close this now as this is implemented: https://vuejs.org/api/utility-types.html#mayberef | 2023-05-27T10:07:15 | 2023-05-27T10:07:15 | {} | NONE |
vuejs | core | 1,569,838,554 | 7,267 | stondbringa | Issue is fixed in v3.3.4. Tested on Safari on iOS < 12 and firefox < 72 | 2023-05-31T09:34:11 | 2023-05-31T09:34:11 | {} | NONE |
vuejs | core | 1,571,094,686 | 5,844 | Triloworld | Confirm as comment: https://github.com/vuejs/core/pull/5952#issuecomment-1523358427
Is deal breaker . We entirely disable animation and this stop people from migration to new version of framework - it is disabled by this issue on main repo from 3.0.0-rc.13 onwards by default (https://github.com/nuxt/nuxt/releases/tag/... | 2023-05-31T23:32:30 | 2023-05-31T23:32:30 | {
"+1": 16
} | NONE |
vuejs | core | 1,573,004,319 | 8,319 | WormGirl | update vue to 3.3.4,i got some error like this.
```js
Property "$t" does not exist on type "{ $: ComponentInternalInstance; $data: {}; $props: { style?: unknown; ref?: VNodeRef | undefined; key?: string | number | symbol | undefined; ref_for?: boolean | undefined; ... 7 more ...; class?: unknown; }; ... 10 more ...; ... | 2023-06-02T01:35:08 | 2023-06-02T01:35:08 | {} | NONE |
vuejs | core | 1,573,007,463 | 8,319 | WormGirl | when i use vue 3.2.x, do not has this error | 2023-06-02T01:38:15 | 2023-06-02T01:38:15 | {} | NONE |
vuejs | core | 1,576,513,623 | 8,501 | shaileshnighojkar | @Fuzzyma @LinusBorg
As per documentation - https://vuejs.org/api/reactivity-advanced.html#shallowreactive
<img width="744" alt="Screenshot" src="https://github.com/vuejs/core/assets/99124848/abeaca77-1e6f-4e7f-8dd1-8b45e15ea964">
<br /><br />
Since they stored are as-is, I tried to log the Map which is pas... | 2023-06-05T10:11:28 | 2023-06-05T10:11:28 | {} | NONE |
vuejs | core | 1,566,771,768 | 8,449 | modelair | Go to docs and read about it.
if u want boolean to be undefined, make it undefined with defaults.
```ts
const props = withDefaults(defineProps<Props>(), {
prop: undefined,
})
``` | 2023-05-29T08:43:38 | 2023-05-29T08:44:57 | {} | NONE |
vuejs | core | 1,567,889,153 | 8,450 | LinusBorg | Using a custom event emitter would be a better way to go. Vue won't support that | 2023-05-30T07:12:47 | 2023-05-30T07:12:47 | {} | MEMBER |
vuejs | core | 1,567,892,491 | 8,452 | LinusBorg | Manually mounting a component with `render` means it's not part of the main app's tree, so it won't be unmounted when a parent unmounts. You would need to unmount it yourself. | 2023-05-30T07:15:27 | 2023-05-30T07:15:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,567,979,742 | 575 | KaelWD | How about `v-slots="$slots"` like jsx?
Full passthrough would just be `<SomeComponent v-bind="$attrs" v-slots="$slots" />`
```html
<SomeComponent v-slots="slots">
<template #foo>
...
```
equivalent to jsx
```jsx
<SomeComponent>
{{
...slots,
foo: () => ...
}}
</SomeComponent>
``` | 2023-05-30T08:17:57 | 2023-05-30T12:05:33 | {
"+1": 13
} | CONTRIBUTOR |
vuejs | core | 1,571,161,842 | 7,910 | mannymu | <img width="647" alt="image" src="https://github.com/vuejs/core/assets/15630104/750c8edc-c07b-4dc5-aa25-4306b2ccc626">
| 2023-06-01T01:01:23 | 2023-06-01T01:01:23 | {} | NONE |
vuejs | core | 1,572,809,583 | 6,420 | ivanmem | Actual in vue 3.3.4 | 2023-06-01T21:27:28 | 2023-06-01T21:27:28 | {} | NONE |
vuejs | core | 1,576,252,032 | 8,500 | LinusBorg | You don't actually need `key` on v-for loops in Vue 3:
https://v3-migration.vuejs.org/breaking-changes/key-attribute.html | 2023-06-05T07:47:25 | 2023-06-05T07:47:25 | {} | MEMBER |
vuejs | core | 1,567,077,478 | 8,449 | edison1105 | @fisheep01
为了对齐原生 HTML 标签的 boolean attributes 的行为。https://developer.mozilla.org/en-US/docs/Glossary/Boolean/HTML | 2023-05-29T12:27:21 | 2023-05-29T12:27:21 | {} | MEMBER |
vuejs | core | 1,572,522,852 | 4,662 | lucasantunes-ciandt | > @raffobaffo would your solution also inject styles into the shadow DOM from child components imported within the `defineCustomElement` component that originate from external packages?
>
> As an example, if I define and export a component with `defineCustomElement`, but within that element is a button component tha... | 2023-06-01T17:47:03 | 2023-06-01T17:47:03 | {} | NONE |
vuejs | core | 1,564,816,891 | 8,416 | rniwa | Thank you! | 2023-05-26T19:10:48 | 2023-05-26T19:10:48 | {} | NONE |
vuejs | core | 1,566,791,409 | 8,449 | fisheep01 | > @fisheep01 https://vuejs.org/guide/components/props.html#prop-validation check it.
我了解文档中的申明，我想表达的是为何针对boolean需要有个额外的逻辑，而不是统一的undefined行为，我觉得这样会给开发者一个额外的理解负担
在实现的时候是因为什么限制或者其他考虑吗？ @modelair | 2023-05-29T09:00:24 | 2023-05-29T09:00:24 | {} | NONE |
vuejs | core | 1,567,898,403 | 8,450 | zouyaoji | It is possible to use custom event, but it is really troublesome and cannot be bound to vue components. But I found a method that may not be conventional, which can continue to trigger events when the vue component is destroyed.
```
const instance = getCurrentInstance()
instance.isUnmounted = false
``` | 2023-05-30T07:19:59 | 2023-05-30T07:19:59 | {} | NONE |
vuejs | core | 1,568,140,263 | 8,452 | wind-rain666 | > Manually mounting a component with `render` means it's not part of the main app's tree, so it won't be unmounted when a parent unmounts. You would need to unmount it yourself.
Thanks, how to unmount it?I can't find any way to do it in documentation. @LinusBorg | 2023-05-30T09:53:36 | 2023-05-30T09:58:56 | {} | NONE |
vuejs | core | 1,569,838,048 | 7,268 | stondbringa | I confirm, issue is fixed in v3.3.4. Tested on Safari on iOS < 12 and firefox < 72 | 2023-05-31T09:33:51 | 2023-05-31T09:33:51 | {} | NONE |
vuejs | core | 1,570,276,443 | 8,310 | emilyAzz | Hello, I have vue version 3.3.4 and upon using the generic type within the defineProps with defaults value managad with the new updates to make it work but when I come to build I encounter the below error with the defineEmits when I am emitting a generic type back
`error TS5088: The inferred type of 'default' refere... | 2023-05-31T13:49:44 | 2023-05-31T13:49:44 | {
"confused": 4,
"eyes": 1
} | NONE |
vuejs | core | 1,570,665,843 | 5,952 | davidwebca | We rely on this in our workflow, this seems to happen only when JS transitions are used and with mode "out-in" if I'm not wrong. Commenting to follow updates. | 2023-05-31T17:54:33 | 2023-05-31T17:54:33 | {} | NONE |
vuejs | core | 1,571,348,832 | 8,466 | tragid | Why not? This is valid type. Maybe at least it is possible throw an exception on build time that enums are not supported?
Also noticed, that this bug is reproduced only when enum value, and strings are mixed within event names.
When only enum values are represented in Emit type - everything is working properly
Wor... | 2023-06-01T05:10:17 | 2023-06-01T05:10:17 | {} | NONE |
vuejs | core | 1,571,887,765 | 8,466 | edison1105 | > Why not? This is valid type. Maybe at least it is possible throw an exception on build time that enums are not supported?
>
> Also noticed, that this bug is reproduced only when enum value, and strings are mixed within event names. When only enum values are represented in Emit type - everything is working properly... | 2023-06-01T11:39:20 | 2023-06-01T11:41:22 | {} | MEMBER |
vuejs | core | 1,572,874,484 | 3,948 | darylblake | The current work around is a bit silly but the only way to remove all the warnings etc. Would it be worthwhile having another PropType primitive like NullablePropType? such as `type: Object as NullablePropType<MyType>` instead of writing `type: null as unknown as Object as PropType<MyType|null>` | 2023-06-01T22:29:10 | 2023-06-01T22:29:10 | {} | NONE |
vuejs | core | 1,577,892,599 | 6,334 | HMoonLy | Did you find a workaround? | 2023-06-06T04:38:19 | 2023-06-06T04:38:19 | {} | NONE |
vuejs | core | 1,578,886,289 | 8,501 | Fuzzyma | @shaileshnighojkar I disagree. as-is means, that nothing is changed in whatever object you pass to shallowReactive.
Since you pass a reactive object, that exposes every property (and doesnt expose refs), shallowReactive should leave it untouched and just also return every property as before. A reactive object should b... | 2023-06-06T14:35:08 | 2023-06-06T14:37:22 | {
"+1": 1
} | NONE |
vuejs | core | 1,564,645,819 | 8,279 | yyx990803 | closed via d621d4c6 | 2023-05-26T16:34:43 | 2023-05-26T16:34:43 | {
"+1": 1,
"hooray": 1
} | MEMBER |
vuejs | core | 1,565,320,641 | 8,373 | jd-solanki | Hey @ml1nk Can you try using `ReturnType` instead of `InstanceType`
Reference: https://github.com/vuejs/language-tools/issues/3206#issuecomment-1563399071 | 2023-05-27T10:09:44 | 2023-05-27T10:09:44 | {} | NONE |
vuejs | core | 1,566,778,323 | 8,449 | fisheep01 | >
基于withDefaults实现当然是可以的，但是我并不希望通过这种方式主动申明，我认为可选的boolean类型应该和可选的number类型或者string类型有一样的表现，而不是直接输出false @modelair | 2023-05-29T08:49:33 | 2023-05-29T08:50:11 | {} | NONE |
vuejs | core | 1,566,784,862 | 8,450 | zouyaoji | Ok, then I'll consider using mitt to do it myself. | 2023-05-29T08:55:55 | 2023-05-29T08:55:55 | {} | NONE |
vuejs | core | 1,568,158,736 | 8,452 | LinusBorg | `render(null, wrapperRef.value)` | 2023-05-30T10:05:39 | 2023-05-30T10:05:39 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,568,277,132 | 575 | IlCallo | This last one seems more "correct" than the initially proposed one | 2023-05-30T11:35:18 | 2023-05-30T11:35:18 | {} | NONE |
vuejs | core | 1,572,396,859 | 5,303 | mannok | Can't believe this could be a Vue issue, I would rather this is my fault | 2023-06-01T16:44:13 | 2023-06-01T16:44:13 | {} | NONE |
vuejs | core | 1,573,826,435 | 5,657 | drossner | > It seems, although not yet clear, that when I replace the root tag, which contains a v-if directive, with a tag, and then make changes in my CustomComponent, it triggers the bug. I hope this information is not misleading.
This helped a lot, in my case, removing a v-if from the top level of a template resolved the ... | 2023-06-02T14:25:31 | 2023-06-02T14:25:31 | {
"+1": 2
} | NONE |
vuejs | core | 1,574,930,788 | 8,478 | shaileshnighojkar | @Bobsans Why do you want to use Proxy directly when you have ref/reactive?
Here is the line where __v_isRef accessedhttps://github.com/vuejs/core/blob/a95e612b252ae59eaf56e0b8ddba66948d4ac20e/packages/reactivity/src/ref.ts#L80
In template unref is used to avoid .value access
https://github.com/vuejs/core/blob/a... | 2023-06-03T12:58:21 | 2023-06-03T12:58:21 | {} | NONE |
vuejs | core | 1,576,084,422 | 5,993 | Flysky12138 | 使用 Nuxt3 时遇到同样的问题。我的 script 块中有个 `await useFetch` 请求，当请求未完成（即：组建未加载完成），切换走，再切换回来，就会出现同样的问题。 | 2023-06-05T05:51:16 | 2023-06-05T05:51:16 | {} | NONE |
vuejs | core | 1,566,782,994 | 8,449 | modelair | @fisheep01 https://vuejs.org/guide/components/props.html#prop-validation check it. | 2023-05-29T08:53:59 | 2023-05-29T08:53:59 | {} | NONE |
vuejs | core | 1,567,995,993 | 8,140 | gVguy | > Interestingly it only occurs on windows build agents, MacOS
Can't confirm this, for me it occured on MacOS | 2023-05-30T08:28:45 | 2023-05-30T08:28:45 | {} | NONE |
vuejs | core | 1,537,992,744 | 7,942 | baiwusanyu-c | the style order problem is caused by the anchor, I updated the code | 2023-05-08T08:50:47 | 2023-05-30T08:50:48 | {} | MEMBER |
vuejs | core | 1,569,842,487 | 7,268 | edison1105 | @stondbringa @TNGD-YQ
thanks. | 2023-05-31T09:36:34 | 2023-05-31T09:36:34 | {} | MEMBER |
vuejs | core | 1,575,479,763 | 8,491 | liuseen-l | 看上去不像一个bug，而是使用方式不太对，这样直接替换对象，本质上没有对原先数组进行操作，因此不会触发更新 | 2023-06-04T09:05:37 | 2023-06-04T09:05:37 | {} | CONTRIBUTOR |
vuejs | core | 1,575,763,201 | 6,978 | oceangravity | > Months have passed, but there has been no progress.
> The same issue still persists. I don't understand why such an obvious issue has not been fixed yet.
There is already a PR for this issue but it needs approval 🫠 | 2023-06-04T22:56:03 | 2023-06-04T22:56:03 | {} | NONE |
vuejs | core | 1,578,503,312 | 8,506 | Alfred-Skyblue | > @Alfred-Skyblue
>
> We need to call `catch` method to handle errors.
>
> https://github.com/vuejs/core/blob/a95e612b252ae59eaf56e0b8ddba66948d4ac20e/packages/runtime-core/src/apiSetupHelpers.ts#L516
>
>
> https://github.com/vuejs/core/blob/a95e612b252ae59eaf56e0b8ddba66948d4ac20e/packages/runtime-core/src/... | 2023-06-06T11:12:23 | 2023-06-06T11:12:23 | {} | MEMBER |
vuejs | core | 1,567,119,559 | 6,256 | Ttou | hope merged quickly | 2023-05-29T13:07:26 | 2023-05-29T13:07:26 | {
"+1": 5
} | NONE |
vuejs | core | 1,567,244,169 | 4,968 | haoqunjiang | Supported now. | 2023-05-29T14:59:25 | 2023-05-29T14:59:25 | {} | MEMBER |
vuejs | core | 1,568,167,615 | 8,452 | wind-rain666 | Thanks, it works. @LinusBorg | 2023-05-30T10:11:57 | 2023-05-30T10:11:57 | {} | NONE |
vuejs | core | 1,574,963,230 | 8,491 | shaileshnighojkar | @haorenJava
Not getting [Vue warn] in the console after opening 'minimal reproduction' link.
```js
detail = resp.data.detail;
```
Here, you are assigning new variable to detail which not reactive hence you are not getting expected result.
Just incase you want reactivity you can use `detail = reactive(res... | 2023-06-03T13:53:56 | 2023-06-03T13:53:56 | {
"+1": 1
} | NONE |
vuejs | core | 1,576,546,303 | 8,474 | shaileshnighojkar | @zhangenming The third gets converted to fourth one ie, third and fourth are same
```html
<slot v-bind="{ name: customName }"></slot>
```
Here you are passing 'name' as a data to the slot content.
Also, your expression does not specify the slot name. which can be specified by 'name' attribute to slot tag. Si... | 2023-06-05T10:36:31 | 2023-06-05T10:36:31 | {} | NONE |
vuejs | core | 1,577,867,957 | 8,509 | edison1105 | I don't think it's a bug, if remove the content that would be a breaking change. you can remove content by disabling the teleport. [see](https://play.vuejs.org/#__DEV__eNqdVE2Pm0AM/SteLpNISWilnrIhathL97CnVuqh6YGASVAGBjEDLUL893rMR0CpdrV7YsZ+fjbPDxrnkOebqkRn6+x0WCS5AY2mzPfHDCBJc1UYaKDAGFqIC5WCILB4nGSfVJof+tzG5ZslvMP4M4w/... | 2023-06-06T04:00:53 | 2023-06-06T04:47:18 | {} | MEMBER |
vuejs | core | 1,566,426,079 | 7,910 | mannymu | <img width="613" alt="image" src="https://github.com/vuejs/core/assets/15630104/bdfefdc3-8180-4b45-9c8e-343d2e64a6f4">
<img width="792" alt="image" src="https://github.com/vuejs/core/assets/15630104/6fe7f446-8a11-4e9a-ad32-2cf684a0643a">
| 2023-05-29T02:58:22 | 2023-05-29T02:58:22 | {} | NONE |
vuejs | core | 1,567,814,149 | 8,373 | ml1nk | I tried it with ReturnType and ComponentExposed but neither one works. | 2023-05-30T06:14:49 | 2023-05-30T06:14:49 | {
"+1": 1
} | NONE |
vuejs | core | 1,571,125,443 | 8,459 | lkwilson | So is it bug if they are not unmounting when the comment is removed then?
```
<script setup>
const toggle = ref(true)
...
</script>
...
<template v-if="toggle">
<Loud key="one" val="hi" />
</template
<template v-else>
<Loud key="one" val="hey" />
</template>
```
It renders hi, but on toggle, never re... | 2023-06-01T00:08:21 | 2023-06-01T00:08:21 | {} | NONE |
vuejs | core | 1,572,310,624 | 8,466 | tragid | > > Why not? This is valid type. Maybe at least it is possible throw an exception on build time that enums are not supported?
> > Also noticed, that this bug is reproduced only when enum value, and strings are mixed within event names. When only enum values are represented in Emit type - everything is working properly... | 2023-06-01T15:52:03 | 2023-06-01T15:52:03 | {} | NONE |
vuejs | core | 1,575,034,715 | 8,484 | shaileshnighojkar | @1020847665 You are watching on `state.obj` and then assigning it a new value to it. In that case that watcher will not get triggered.
```js
const obj = reactive({
child: {
key: 'value'
}
})
watch(obj, (val) => console.log('watch obj', val), { deep: true }) // triggered
watch(obj.child, (val) =>... | 2023-06-03T15:54:08 | 2023-06-03T15:54:08 | {
"+1": 1
} | NONE |
vuejs | core | 1,575,884,282 | 8,494 | hibichann | ```html
<template>
<h1>{{
1/*123*/
}}
</h1>
</template>
```
you can use /**/ | 2023-06-05T00:48:41 | 2023-06-05T00:48:41 | {} | NONE |
vuejs | core | 1,538,010,657 | 7,942 | baiwusanyu-c | > the style order problem is caused by the anchor, I updated the code
I marked the style of each child component with a timestamp, which allows them to be found and deleted when the component is unloaded, but I think the timestamp does not seem elegant. I tried to use hash-sum, but found that it would Makes it nece... | 2023-05-08T08:59:18 | 2023-05-30T08:50:54 | {} | MEMBER |
vuejs | core | 1,569,845,511 | 7,267 | edison1105 | closed via https://github.com/vuejs/core/commit/91f1c62e6384a8b09f90e7e43b8d347901e529a0 | 2023-05-31T09:38:52 | 2023-05-31T09:38:52 | {} | MEMBER |
vuejs | core | 1,572,452,495 | 8,459 | lkwilson | Ok, cool. Thanks for taking time to respond. I see how this is undefined behavior territory now | 2023-06-01T17:08:05 | 2023-06-01T17:08:05 | {} | NONE |
vuejs | core | 1,573,880,804 | 6,766 | Anoesj | > Unfortunately this is because ref values have to expose the "unwrapped" type, which unwraps nested refs, to ensure value access correctness:
>
> ```ts
> const a = { b: ref(0) }
> const c = ref(a)
>
> c.value.b // should be number
>
> c.value = a // same error you saw
> ```
>
> To fix this we will need ... | 2023-06-02T15:02:39 | 2023-06-02T15:03:16 | {
"+1": 9
} | NONE |
vuejs | core | 1,575,987,127 | 8,494 | liuseen-l | > ```
> <template>
> <h1>{{
> 1/*123*/
> }}
> </h1>
> </template>
> ```
>
如果单从能实现需求上，确实可以选择你说的这种方式来解决这个问题
但是从健壮性来看，这个在开发时给人的直观感受是没有问题的，但是却得到一个error，并且无法定位到错误位置，一时间会给人不知所措的感觉，修改成本不大https://github.com/vuejs/core/pull/8493
<img width="256" alt="image" src="https://github.com/vuejs/core/assets/910... | 2023-06-05T03:31:36 | 2023-06-05T04:45:45 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,577,008,241 | 8,506 | Alfred-Skyblue | The Promise A+ specification does not describe that a PromiseLike must necessarily have a `catch` method. In fact, the `catch` method is part of the ECMAScript 2015 specification. Should we consider removing the detection of the `catch` method?
| 2023-06-05T15:20:36 | 2023-06-05T15:20:36 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.