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,654,061,270 | 1,825 | jonathanjameswatson | It looks like this issue was closed due to commit https://github.com/vuejs/core/commit/128ec460ec00ca8672352d019b264c80dfd0c3b0.
This commit indirectly solves this issue for `.number` and `.trim` modifiers by applying their effects to `v` in `emit('update:modelValue', v)` on the wrapper component. `v` itself from th... | 2023-07-27T17:17:54 | 2023-07-27T17:17:54 | {} | NONE |
vuejs | core | 1,644,889,836 | 8,817 | mnm1001 | >
yes, it is my question
i know maybe if i called 'params.value.a' in computed like this
```
Vue.computed(() => {
params.value.a
const originalArgs =Vue.toRaw(Vue.unref(params))
const storeKey = JSON.stringify(originalArgs)
return storeKey
})
```
when 'params.valu... | 2023-07-21T02:10:49 | 2023-07-21T02:10:49 | {} | NONE |
vuejs | core | 1,648,768,709 | 8,286 | brunoalod | Any news about this? | 2023-07-24T23:47:18 | 2023-07-24T23:47:18 | {
"+1": 7
} | NONE |
vuejs | core | 1,648,921,643 | 8,834 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 4c0748b95b5d42fcff7f0ceb7ebf1a484d54b619 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2023-07-25T02:41:13 | 2023-07-25T02:45:33 | {} | NONE |
vuejs | core | 1,652,084,896 | 4,668 | ttencate | Also ran into this. Also noticed that it's not entirely deterministic. Removing the output directory and doing a fresh build seems to reliably trigger it for me.
A simple fix might be to unconditionally prefix these parameters with an underscore in the generated code: `_$props`, `_$setup`, `_$options` (and also `_$d... | 2023-07-26T15:48:37 | 2023-07-26T15:49:27 | {
"heart": 1
} | NONE |
vuejs | core | 1,652,841,334 | 8,852 | Shyam-Chen | Required:
```vue
<script lang="ts" setup>
const props = defineProps<{
b1: boolean;
b2: boolean;
b3: boolean;
s1: string;
s2: string;
}>();
</script>
```
Optional:
```vue
<script lang="ts" setup>
const props = defineProps<{
b1?: boolean;
b2?: boolean;
b3?: boolean;
s1?: string;... | 2023-07-27T03:01:34 | 2023-07-27T03:02:36 | {} | CONTRIBUTOR |
vuejs | core | 1,655,641,851 | 8,860 | norahmaria | Oh, okay, thanks @LinusBorg. It's the non-top level properties of an object that do not work, but from what I understand that means the use of `style.padding` below in the template shouldn't work either (even though it looks like it does when I test it), or am I misunderstanding something?
```vue
<script lang="ts" se... | 2023-07-28T12:56:00 | 2023-07-28T12:59:05 | {} | NONE |
vuejs | core | 1,645,201,776 | 5,002 | cmath10 | Any updates? In my application, I create smaller Vue apps for custom tooltips, and Inject API can significantly reduce the number of options I need to pass to my directive. | 2023-07-21T08:22:28 | 2023-07-21T08:23:22 | {} | NONE |
vuejs | core | 1,649,722,343 | 8,837 | FreekVR | Yeah, I had some cases where I had to do that, although I am not sure why. If you don't need the index (my eslint config doesn't like unused variables) then `v-for="name in Object.keys($slots)` works even better :) | 2023-07-25T12:12:27 | 2023-07-25T12:12:27 | {
"+1": 1
} | NONE |
vuejs | core | 1,652,192,060 | 8,842 | pleek91 | > ```
> <DateLabel :value="dateGetter()" />
> ```
@Shyam-Chen I could be wrong but I believe there is a distinct difference between that and what I'm asking for. A getter normalized to a ref using `toRef` calls the getter itself each time `.value` is accessed. Which would make this work differently in a few ways
... | 2023-07-26T17:02:47 | 2023-07-26T17:02:47 | {} | NONE |
vuejs | core | 1,655,414,059 | 8,857 | laurens94 | Idem when using [toValue](https://vuejs.org/api/reactivity-utilities.html#tovalue) | 2023-07-28T09:57:41 | 2023-07-28T09:57:41 | {} | NONE |
vuejs | core | 1,645,671,745 | 8,817 | edison1105 | @mnm1001 this is because Vue does not track a raw value. | 2023-07-21T14:21:11 | 2023-07-21T14:21:11 | {} | MEMBER |
vuejs | core | 1,654,867,285 | 8,852 | caohongzhi1 | PropType一般用于定义复杂变量（例如：数组、对象、函数）的类型定义，布尔类型或字符串类型直接定义即可，PropType会造成prop变量接口定义为可选变量。 | 2023-07-28T02:03:13 | 2023-07-28T02:03:13 | {} | NONE |
vuejs | core | 1,655,648,055 | 8,860 | LinusBorg | Priting a ref out to the template in an interpolation ({{}}) is a special case as it needs to be converted to a string by Vue, and that process unwraps it.
We are aware that this is a bit inconsistent, but that's rhe way it was designed for v3 and will stay until the next major at least. | 2023-07-28T13:00:47 | 2023-07-28T13:00:47 | {} | MEMBER |
vuejs | core | 1,656,536,314 | 8,354 | yangzl96 | > I can't see the render function binding a click event in your example github repo. EDIT: it would also be much better to put the example on https://sfc.vuejs.org/ because there is no special build required.
Thanks. I added the code , updated repo | 2023-07-29T03:15:34 | 2023-07-29T03:15:34 | {} | NONE |
vuejs | core | 1,644,900,882 | 5,110 | aszx0413 | still a bug | 2023-07-21T02:29:28 | 2023-07-21T02:29:28 | {} | NONE |
vuejs | core | 1,650,704,009 | 6,951 | StitiFatah | Any workaround for this ? How are you guys dealing with this problem ? Using third party libraries (seems to work with vueuse motion) ? | 2023-07-25T23:32:38 | 2023-07-25T23:32:38 | {
"+1": 1
} | NONE |
vuejs | core | 1,652,936,624 | 8,475 | hymair | Will this be merged soon? | 2023-07-27T05:27:58 | 2023-07-27T05:27:58 | {} | NONE |
vuejs | core | 1,653,118,593 | 8,354 | rocifier | I can't see the render function binding a click event in your example github repo. EDIT: it would also be much better to put the example on https://sfc.vuejs.org/ because there is no special build required. | 2023-07-27T08:14:12 | 2023-07-27T08:19:26 | {} | NONE |
vuejs | core | 1,655,649,583 | 8,860 | norahmaria | @LinusBorg alright, makes sense, thanks for the quick response! | 2023-07-28T13:02:01 | 2023-07-28T13:02:01 | {} | NONE |
vuejs | core | 1,657,452,833 | 8,872 | Justineo | https://vuejs.org/api/component-instance.html#emit
```ts
interface ComponentPublicInstance {
$emit(event: string, ...args: any[]): void
}
```
`$emit` accepts multiple arguments. | 2023-07-31T03:31:11 | 2023-07-31T03:31:11 | {} | MEMBER |
vuejs | core | 1,648,844,156 | 8,830 | baiwusanyu-c | In this pr, if sfc is rendered as a custom element, the css variables of its normal element tags (div, span...) will be promoted to the style attribute of the tag of the custom element, and it is compatible with pr #7942
```
// before
<my-custom-el>
<span style="--color: red;"> hello </span>
</my-custom-el>
``... | 2023-07-25T01:49:16 | 2023-07-25T01:49:16 | {} | MEMBER |
vuejs | core | 1,648,921,198 | 8,834 | vercel[bot] | @bigfatDone is attempting to deploy a commit to the **vuejs** Team on [Vercel](https://vercel.com).
A member of the Team first needs to [authorize it](https://vercel.com/git/authorize?team=vuejs&type=github&job=%7B%22headInfo%22%3A%7B%22sha%22%3A%221fb523fa01c8179ff93ef88080dac013cbd22713%22%7D%2C%22id%22%3A%22QmcfZoa... | 2023-07-25T02:40:57 | 2023-07-25T02:40:57 | {} | NONE |
vuejs | core | 1,648,921,718 | 8,834 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 4c0748b95b5d42fcff7f0ceb7ebf1a484d54b619 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2023-07-25T02:41:15 | 2023-07-25T02:45:33 | {} | NONE |
vuejs | core | 1,649,707,903 | 8,837 | marfalkov | @FreekVR Another thing that'll make this component work is `v-for="(name, index) in Object.keys($slots)"`
[stackblitz](https://stackblitz.com/edit/github-u4xmkj-iqvarw?file=src%2Fcomponents%2FExtend.vue) | 2023-07-25T12:05:50 | 2023-07-25T12:05:50 | {} | NONE |
vuejs | core | 1,650,013,919 | 8,837 | marfalkov | > Yeah, I had some cases where I had to do that, although I am not sure why.
It's because the $slots is a proxy object. | 2023-07-25T15:02:55 | 2023-07-25T15:02:55 | {} | NONE |
vuejs | core | 1,650,855,475 | 8,662 | yangliguo7 | I'm not sure if this is a problem.
from the source code. when u use `push` to add a value to array. The added value is not changed
https://github.com/vuejs/core/blob/3be4e3cbe34b394096210897c1be8deeb6d748d8/packages/reactivity/src/baseHandlers.ts#L75-L84
` (toRaw(this) as any)[key].apply(this, args) `
but if ... | 2023-07-26T01:56:52 | 2023-07-26T01:56:52 | {} | CONTRIBUTOR |
vuejs | core | 1,651,098,155 | 8,847 | xinchao-zhang | I see, thanks. Mystery solved then, I will close this. | 2023-07-26T07:04:42 | 2023-07-26T07:04:42 | {} | NONE |
vuejs | core | 1,645,600,979 | 7,861 | vercel[bot] | @edison1105 is attempting to deploy a commit to the **vuejs** Team on [Vercel](https://vercel.com).
A member of the Team first needs to [authorize it](https://vercel.com/git/authorize?team=vuejs&type=github&job=%7B%22headInfo%22%3A%7B%22sha%22%3A%227f2205ec60eb4e01c0d85fb7500e4033f324e121%22%7D%2C%22id%22%3A%22QmNnonG... | 2023-07-21T13:35:22 | 2023-07-21T13:35:22 | {} | NONE |
vuejs | core | 1,649,661,977 | 8,837 | FreekVR | Thanks, not sure how that mistake crept into my project, I seem to remember having it the other way around and that not working either. But this seems to remedy the issue. | 2023-07-25T11:36:12 | 2023-07-25T11:36:12 | {
"+1": 1,
"heart": 1
} | NONE |
vuejs | core | 1,651,091,990 | 8,847 | xinchao-zhang | I was referring to this: https://vuejs.org/guide/essentials/watchers.html#deep-watchers
But on a second look, it says “if you call watch directly on a reactive object” - does this mean the behavior literally applies only to things created using reactive(), not ref() of an object, or ref whose value is set to a react... | 2023-07-26T06:59:32 | 2023-07-26T06:59:32 | {} | NONE |
vuejs | core | 1,656,031,171 | 8,862 | LinusBorg | Even if this were a bug, you would have to file it with thr nuxt project as Vue core has nothing to do with the auto-import functionality of nuxt. | 2023-07-28T17:11:17 | 2023-07-28T17:11:32 | {} | MEMBER |
vuejs | core | 1,648,996,661 | 8,834 | Justineo | Please **DO NOT** abuse pull requests. Do experiments in your own repo. Thanks. | 2023-07-25T03:24:36 | 2023-07-25T03:24:36 | {} | MEMBER |
vuejs | core | 1,649,772,297 | 8,348 | edison1105 | @ColinLQ `UploadProps` is a very complex type and not supported, you should use `/* @vue-ignore */` ignore it. | 2023-07-25T12:45:47 | 2023-07-25T12:45:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,652,842,477 | 8,842 | Shyam-Chen | Use `computed`?
```vue
<script lang="ts" setup>
import { ref, computed } from 'vue';
import DateLabel from './DateLabel.vue';
const dateConst = new Date();
const dateRef = ref(new Date());
const dateGetter = computed(() => new Date());
</script>
<template>
<DateLabel :value="dateConst" />
<DateLa... | 2023-07-27T03:03:20 | 2023-07-27T03:06:42 | {} | CONTRIBUTOR |
vuejs | core | 1,652,933,188 | 8,466 | hymair | I can confirm this seems to be a bug. We are using enums to define all our events and they are not picked up by Vue. Results in events being executed twice. | 2023-07-27T05:23:15 | 2023-07-27T05:24:33 | {} | NONE |
vuejs | core | 1,654,245,329 | 8,825 | scottbedard | On first glance, it looks like the array types may be coming from the `string[]` part of this union
https://github.com/vuejs/core/blob/3be4e3cbe34b394096210897c1be8deeb6d748d8/packages/runtime-core/src/componentProps.ts#L44-L46 | 2023-07-27T18:53:24 | 2023-07-27T18:53:24 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,656,039,611 | 8,858 | posva | https://github.com/vuejs/vue/issues/13060 is the correct one 👍 | 2023-07-28T17:19:05 | 2023-07-28T17:19:05 | {} | MEMBER |
vuejs | core | 1,637,841,105 | 8,149 | LeaVerou | @WhereJuly Your workaround requires coupling Vue with the class using the private properties, however these may be developed entirely separately. E.g. in my case, I was handling [`Color`](https://colorjs.io/) objects with Vue, and Color.js is a library that has nothing to do with Vue whatsoever (I’ve since filed an iss... | 2023-07-17T10:35:16 | 2023-07-17T10:35:16 | {} | NONE |
vuejs | core | 1,638,267,552 | 8,522 | solmanter | It worked. Thanks @edison1105 | 2023-07-17T14:29:43 | 2023-07-17T14:29:43 | {} | NONE |
vuejs | core | 1,639,048,167 | 4,314 | gnuletik | Hi @mjschranz, I'm not sure about the latest versions of Vue. I did not test it.
You may have a chance to make it work by rebasing the PR on main. | 2023-07-17T23:49:56 | 2023-07-17T23:49:56 | {} | NONE |
vuejs | core | 1,641,285,024 | 8,759 | Shyam-Chen | Use `vue-cli`. `vue-cli` is based on `webpack`. | 2023-07-19T02:22:37 | 2023-07-19T02:24:15 | {} | CONTRIBUTOR |
vuejs | core | 1,641,459,760 | 8,788 | klausXR | > Use `ref` and Custom Directives.
Can you elaborate on that?
Are you suggesting that I create a custom directive and add that to the `attributes` object, so that it gets bound to the element?
As far as I'm aware the `withDirectives` helper works only inside render functions, is there a way to add a directiv... | 2023-07-19T05:54:14 | 2023-07-19T05:55:30 | {} | NONE |
vuejs | core | 1,641,883,064 | 8,804 | jacekkarczmarczyk | Use typescript? | 2023-07-19T11:07:38 | 2023-07-19T11:07:38 | {
"-1": 1
} | CONTRIBUTOR |
vuejs | core | 1,643,343,130 | 8,756 | Shyam-Chen | Ah! I didn't look carefully, but currently, I have separated Button and Link into two separate components. | 2023-07-20T06:35:11 | 2023-07-20T06:35:11 | {} | CONTRIBUTOR |
vuejs | core | 1,635,183,489 | 7,987 | transtone | https://github.com/vuejs/core/pull/8701 | 2023-07-14T02:41:34 | 2023-07-14T02:41:34 | {} | NONE |
vuejs | core | 1,635,188,640 | 8,780 | zh-lx | In native HTML, the width of <img /> can be expressed in units. It is obvious that the content of this part in MDN is inconsistent with the behavior of native HTML. How can you ensure that the content of MDN is always correct? | 2023-07-14T02:49:57 | 2023-07-14T02:49:57 | {} | CONTRIBUTOR |
vuejs | core | 1,635,310,159 | 8,779 | epreston | It seems that "sfc-playground" is missing `"type": "module",` in the package.json.
That fixes the issue.
The second way to fix the issue is adding the missing `"execa": "^4.0.2",` as dependency in the sfc-playground's package.json, then, removing the changes just in this private project.
The third way looks ... | 2023-07-14T05:47:59 | 2023-07-14T06:02:12 | {} | NONE |
vuejs | core | 1,635,583,746 | 7,775 | basil-gor | Got the same issue using `vue-datepicker` inline styles
```
<component :is="'style'">
{{ datepickerStyles }}
</component>
```
I hope #7776 will be merged some day! | 2023-07-14T09:33:54 | 2023-07-14T09:33:54 | {} | CONTRIBUTOR |
vuejs | core | 1,635,922,649 | 8,780 | Justineo | > For example, sometimes users may add an attribute to the dom that is not in the HTML specification and unify the dom with that attribute.
That’s not the case here. Vue only sets bindings as properties if they exist on the element. Unknown attributes are always set as-is. | 2023-07-14T14:11:15 | 2023-07-14T14:11:47 | {} | MEMBER |
vuejs | core | 1,637,295,354 | 8,783 | baiwusanyu-c | This is different from 7775. The essential problem of 8783 is that it uses `contentful-rich-text-vue-renderer` (it uses the h function internally). In this process, the virtual nodes generated by both the server and the client are generated by `contentful-rich -text-vue-renderer` control. Therefore, since the virtual n... | 2023-07-17T02:28:25 | 2023-07-17T02:28:25 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,639,548,413 | 8,790 | edison1105 | @Mario34 <s>see https://github.com/vuejs/core/issues/5363#issuecomment-1509175693
Chrome doesn't seem to fix the problem in #5363 and `I tested the case where there was a memory leak without `svg` based on your demo.`</s>
I tested #5363 and it was fixed, the reviews misled me.
And no svg node does not have a memor... | 2023-07-18T06:06:26 | 2023-07-18T07:12:04 | {} | MEMBER |
vuejs | core | 1,641,279,526 | 8,718 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/5594228416)
| suite | result |
|-------|--------|
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/5594228416/jobs/10228857946) | :white_check_mark: success |
| [pinia](https://github.com/vuejs/ecosystem-ci/actions/runs/5594228... | 2023-07-19T02:14:01 | 2023-07-19T02:22:41 | {} | CONTRIBUTOR |
vuejs | core | 1,641,812,184 | 8,804 | Andrioden | A validator only satisfies 1 of 3
- ✅ Vue out-of-box validation array of types
- ❌ Allow PyCharm and other IDE vendors to easily create type hinting based on prop type
- ❌ Allow linters to easily validate vue template according to prop type
| 2023-07-19T10:12:48 | 2023-07-19T10:14:11 | {} | NONE |
vuejs | core | 1,642,988,545 | 8,756 | Shyam-Chen | #8522 | 2023-07-20T01:53:21 | 2023-07-20T01:53:21 | {} | CONTRIBUTOR |
vuejs | core | 1,643,895,238 | 8,819 | antoinematyja | Thanks for your input, it seems like the types for `v-for` are declared here:
https://github.com/vuejs/core/blob/3.2/packages/runtime-core/src/helpers/renderList.ts#L41
And we can see that the second argument `key` gets the type `K` which is `K extends keyof T` (with `T` the type of the v-for source).
So in my case ... | 2023-07-20T13:07:07 | 2023-07-20T13:07:07 | {
"+1": 6
} | NONE |
vuejs | core | 1,644,877,768 | 7,898 | T1c0MmRtODFORlpt | same problem here. | 2023-07-21T01:51:41 | 2023-07-21T01:51:41 | {} | NONE |
vuejs | core | 1,636,500,432 | 7,276 | 719media | This bug affected me unexpectedly today. I assume bandwidth just isn't there to get this reviewed and pushed. Just commenting to keep this thread alive! | 2023-07-14T22:10:21 | 2023-07-14T22:10:21 | {
"+1": 1
} | NONE |
vuejs | core | 1,641,294,483 | 4,397 | youthlin | >
I found this, may help you: @femans
https://github.com/vuejs/language-tools/issues/3206#issuecomment-1624541884 | 2023-07-19T02:37:44 | 2023-07-19T02:37:44 | {} | NONE |
vuejs | core | 1,642,445,450 | 8,811 | so1ve | Yes, I just simply checked if the argument begins with a capital letter. If so, I add a `-` before the result | 2023-07-19T17:02:25 | 2023-07-19T17:02:25 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,642,968,343 | 8,811 | Justineo | @so1ve Hmm I made a mistake when I found `:-foo-bar` actually works in this case. But I’m still not sure what shall we suggest for prop `FooBar` on the Volar side. | 2023-07-20T01:23:35 | 2023-07-20T01:23:35 | {} | MEMBER |
vuejs | core | 1,643,271,165 | 8,756 | viet34tqc | Hi, thanks for your reply.
For some reasons, I cannot get the `href` props even if I pass it in parent component. Here is my code for Button component:
```
<script setup lang="ts">
import clsx from 'clsx'
import type { ButtonHTMLAttributes, LinkHTMLAttributes } from 'vue'
// Here is tailwind class for varia... | 2023-07-20T05:46:30 | 2023-07-20T05:46:30 | {} | NONE |
vuejs | core | 1,634,977,140 | 8,779 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8ad4cc5aa8a40851e75bb5993ef675e7fd8f3891 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2023-07-13T22:03:27 | 2023-07-13T22:03:27 | {} | NONE |
vuejs | core | 1,635,299,153 | 8,779 | sxzz | `execa` >= 6 is pure ESM. https://github.com/sindresorhus/execa/releases/tag/v6.0.0
Which means we cannot use it in CommonJS. | 2023-07-14T05:33:39 | 2023-07-14T05:33:39 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,638,689,778 | 5,767 | sanba-anass | the issue is still there using the latest version of vue , not using any libray just changing a prop does not hot reload anything
iwas using this to get my props :
const props = defineProps(['msg']);
const msg= props.msg
------
switching to this fixes the issue :
const props = defineProps({
msg: {
type: St... | 2023-07-17T18:50:00 | 2023-07-17T19:11:40 | {} | NONE |
vuejs | core | 1,642,010,451 | 8,804 | Andrioden | Hehe.
> I understand the answer might be "you should use TypeScript", but I have a fairly decently typed javascript project, and would like to try to keep it that way while praying [js types will be approved in the future](https://github.com/tc39/proposal-type-annotations).
To add:
While i probably should use... | 2023-07-19T12:39:50 | 2023-07-19T12:57:37 | {
"+1": 1
} | NONE |
vuejs | core | 1,642,173,626 | 8,811 | so1ve | @edison1105 🤔🤔 I guess you need to transfer this issue to vuejs/language-tools :))))))
| 2023-07-19T14:16:47 | 2023-07-19T14:16:47 | {} | MEMBER |
vuejs | core | 1,643,065,581 | 8,811 | Justineo | Or shall we just warn about using PascalCased props? | 2023-07-20T03:46:49 | 2023-07-20T03:46:49 | {} | MEMBER |
vuejs | core | 1,643,590,273 | 8,804 | Andrioden | Updated suggestion list | 2023-07-20T09:29:57 | 2023-07-20T09:29:57 | {} | NONE |
vuejs | core | 1,639,104,246 | 8,576 | matthew-dean | @yyx990803 Here's an even worse, more egregious example, where Vue's type inference is way off-base.
I made a component with these props (I've reduced it to the specific problem):
```ts
interface Props {
error?: string | true
}
defineProps<Props>()
```
Now, _in this case_, the `error` can only have 3 possib... | 2023-07-18T00:40:22 | 2023-07-18T01:14:51 | {
"+1": 9,
"eyes": 3
} | NONE |
vuejs | core | 1,640,213,393 | 6,095 | mostafaznv | any news? | 2023-07-18T13:17:20 | 2023-07-18T13:17:20 | {
"eyes": 3
} | NONE |
vuejs | core | 1,635,192,570 | 8,780 | edison1105 | @zh-lx
we should follow the [spec](https://html.spec.whatwg.org/multipage/embedded-content-other.html#dimension-attributes) | 2023-07-14T02:56:05 | 2023-07-14T02:56:05 | {} | MEMBER |
vuejs | core | 1,636,844,325 | 8,372 | Bernard-Borg | bump - need this please | 2023-07-15T17:58:30 | 2023-07-15T17:58:30 | {} | NONE |
vuejs | core | 1,638,366,129 | 8,797 | christian-bromann | I am aware of the `create-vue` project, I am asking more about the test harness in this repository. | 2023-07-17T15:20:46 | 2023-07-17T15:20:46 | {} | NONE |
vuejs | core | 1,639,114,801 | 8,412 | matthew-dean | I'm getting this same issue with `LabelHTMLAttributes` and adding `/* vue-ignore */` does nothing. The error persists. Note that this same error does not occur with `defineProps` in [unplugin-vue-macros](https://github.com/sxzz/vue-macros), which also supports extending types. | 2023-07-18T00:57:44 | 2023-07-18T00:59:33 | {} | NONE |
vuejs | core | 1,644,649,307 | 6,553 | DrJume | > Ugh, you should **never** use `v-html` on a component. A component is supposed to manage its own DOM tree. Using `v-html` completely defeats the purpose of using a component at all, why not just use it on a plain `<div>`?
>
> We should probably just make this a compile time error.
It is quite practical for reus... | 2023-07-20T21:48:49 | 2023-07-20T21:49:23 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 1,635,157,538 | 8,780 | edison1105 | should be `width="200"` without `px`.
see https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/width
for more detail see https://github.com/vuejs/core/issues/7658
IMO, this should be fixed because the behavior of CSR and SSR is inconsistent, see [SSR](https://play.vuejs.org/#__DEV____SSR__eNqNUctOwzAQ/J... | 2023-07-14T02:01:49 | 2023-07-14T03:17:34 | {} | MEMBER |
vuejs | core | 1,635,396,265 | 8,780 | zh-lx | > > Firstly, contrary to what you said, most browsers support this usage, and in fact, I don't know which browser does not support this usage.
>
> I deleted my comment as I misremembered it from our last discussion about this in #7658. In most cases Vue tries to set properties if they exist. Shall we keep all invali... | 2023-07-14T07:10:33 | 2023-07-14T07:10:33 | {} | CONTRIBUTOR |
vuejs | core | 1,637,666,969 | 8,797 | Shyam-Chen | You can add here https://github.com/vuejs/create-vue/blob/85008f12aa2bb8b298e5f1dffacccf2cdfc43624/index.ts#L222
Currently, there are Cypress, Nightwatch, and Playwright. | 2023-07-17T09:17:54 | 2023-07-17T09:19:10 | {} | CONTRIBUTOR |
vuejs | core | 1,639,057,879 | 8,794 | Shyam-Chen | I am using it.
https://github.com/Shyam-Chen/Vue-Starter/blob/main/src/components/Transfer.vue | 2023-07-18T00:03:53 | 2023-07-18T00:03:53 | {} | CONTRIBUTOR |
vuejs | core | 1,642,217,387 | 8,811 | so1ve | @Justineo
| 2023-07-19T14:39:46 | 2023-07-19T14:39:46 | {} | MEMBER |
vuejs | core | 1,642,438,357 | 8,811 | browsnet | In fact, the `hyphenate` function and the `camelize` function are not reversible to each other.
For example, `camelize(hyphenate('FooBar')) == 'fooBar'`, which has lost the information of the capital letter "F".
Therefore, if language-tools uses hyphenate to achieve the opposite effect of camelize, it must be aware... | 2023-07-19T16:57:10 | 2023-07-19T16:57:10 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,634,355,653 | 8,777 | edison1105 | duplicate of https://github.com/vuejs/core/issues/7238 | 2023-07-13T14:33:12 | 2023-07-13T14:33:12 | {} | MEMBER |
vuejs | core | 1,635,102,372 | 8,778 | edison1105 | IMO, If the user returns a non-VNode, an error should be reported. Because Vue can't handle it. There is no point in giving warnings, and many people don't really care about warnings. | 2023-07-14T00:52:57 | 2023-07-14T00:52:57 | {
"laugh": 2
} | MEMBER |
vuejs | core | 1,635,430,688 | 8,764 | edison1105 | PR welcome | 2023-07-14T07:34:04 | 2023-07-14T07:34:04 | {} | MEMBER |
vuejs | core | 1,636,089,709 | 6,088 | zetaraku | Would this be merged back into Vue 2.7? | 2023-07-14T16:23:17 | 2023-07-14T16:23:17 | {
"+1": 1
} | NONE |
vuejs | core | 1,638,631,988 | 8,576 | matthew-dean | @yyx990803
This statement didn't make sense to me:
> The interface declares foo as being optional, but it is not the type of the resolved runtime props. The resolved props type correctly excludes the undefined type, making it consistent with the runtime behavior.
I'm not sure what you mean "correctly excludes... | 2023-07-17T18:09:32 | 2023-07-17T18:09:32 | {
"+1": 3
} | NONE |
vuejs | core | 1,641,305,212 | 4,309 | simvol | Bump | 2023-07-19T02:50:02 | 2023-07-19T02:50:02 | {} | NONE |
vuejs | core | 1,641,996,792 | 8,811 | edison1105 | /cc @so1ve duty call 🤭 | 2023-07-19T12:30:13 | 2023-07-19T12:30:13 | {
"laugh": 1
} | MEMBER |
vuejs | core | 1,643,245,817 | 8,811 | so1ve | @Justineo that's an edge case IMO. Should vue forbid this usage? | 2023-07-20T05:32:58 | 2023-07-20T05:32:58 | {} | MEMBER |
vuejs | core | 1,643,587,554 | 8,818 | edison1105 | LGTM. | 2023-07-20T09:27:58 | 2023-07-20T09:27:58 | {} | MEMBER |
vuejs | core | 1,634,993,809 | 8,779 | epreston | have I triggered the wrong CI ? | 2023-07-13T22:24:33 | 2023-07-13T22:24:33 | {} | NONE |
vuejs | core | 1,635,192,909 | 8,780 | starcsb | Agree with this issue. Currently, native HTML, react, solid, and svelte can all support width with units, but only Vue does not support it, which is very awkward. | 2023-07-14T02:56:41 | 2023-07-14T02:56:41 | {} | NONE |
vuejs | core | 1,635,197,833 | 8,780 | zh-lx | I agree. But when a user gives an invalid value, vue should keep this value and let the HTML handle it according to browser's standard, rather than handling it at the Vue level. | 2023-07-14T03:02:31 | 2023-07-14T03:02:31 | {
"+1": 6
} | CONTRIBUTOR |
vuejs | core | 1,636,967,217 | 8,783 | edison1105 | Maybe duplicate of https://github.com/vuejs/core/issues/7775
/cc @baiwusanyu-c | 2023-07-16T03:01:36 | 2023-07-16T03:01:36 | {} | MEMBER |
vuejs | core | 1,637,305,887 | 8,783 | edison1105 | thanks @baiwusanyu-c
duplicate of https://github.com/vuejs/core/issues/7285 | 2023-07-17T02:50:11 | 2023-07-17T02:50:27 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,638,694,900 | 4,314 | mjschranz | @gnuletik Reviving an old thread here, but by chance did that PR you write here only work for specific versions?
I'm actually writing a vuejs webcomponent that will consume HTML (that includes vuejs components inside it) from a CMS to be used in an Angular app.
As it stands right now I'm trying to use the file yo... | 2023-07-17T18:53:54 | 2023-07-17T18:53:54 | {
"eyes": 1
} | NONE |
vuejs | core | 1,641,270,572 | 8,804 | Shyam-Chen | Use `validator`? | 2023-07-19T01:58:28 | 2023-07-19T01:58:28 | {} | CONTRIBUTOR |
vuejs | core | 1,641,279,287 | 8,718 | sxzz | /ecosystem-ci run | 2023-07-19T02:13:36 | 2023-07-19T02:13:36 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,641,280,024 | 8,788 | Shyam-Chen | Use `ref` and Custom Directives. | 2023-07-19T02:14:53 | 2023-07-19T02:15:19 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.