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,302,859,872 | 7,014 | edison1105 | I can reproduce it. but I think this might be related to CSS rules. Could you reproduce it after removing all styles?
> and more, if you Uncomment 59 line code `// r[2].part = '反';` this bug will disappear
still can reproduce.
if you remove `display: flex` rule of `body`. It will disappear.
| 2022-11-04T01:49:03 | 2022-11-04T01:52:08 | {} | MEMBER |
vuejs | core | 1,304,413,104 | 6,876 | sxzz | I think we should open this issue for official implementation tracking. | 2022-11-05T05:33:16 | 2022-11-05T05:33:16 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,305,917,121 | 4,294 | sanfords | Inspired by @alsotang and @tewshi, for defineEmits and importing types, this workaround works for us. We had to silence the linter. But the call to emit() is still typesafe. Ty!
```
import { x } from "./i";
interface y extends x {}
// eslint-disable-next-line @typescript-eslint/no-empty-interface
const emit =... | 2022-11-07T17:04:00 | 2022-11-07T17:04:00 | {
"+1": 1,
"-1": 5
} | NONE |
vuejs | core | 1,305,932,290 | 7,051 | qmhc | @sxzz yes, I missed it. Is #3969 plans to be merged recently? | 2022-11-07T17:13:42 | 2022-11-07T17:13:42 | {} | NONE |
vuejs | core | 1,306,526,872 | 6,430 | yyx990803 | Thanks a lot for the PR - it seems to be missing a case (props destructuring) which is included in #6461, so I merged that one istead, I hope you don't mind. | 2022-11-08T02:19:20 | 2022-11-08T02:19:20 | {} | MEMBER |
vuejs | core | 1,299,982,521 | 7,009 | adamjedlicka | Closes #6811 | 2022-11-02T10:11:05 | 2022-11-02T10:13:29 | {} | CONTRIBUTOR |
vuejs | core | 1,302,026,194 | 7,014 | posva | I can't reproduce but also, the scrollbar handling is not related to Vue. My guess is you are relying on a browser side effect related to how elements are updated/inserted/removed but if you want to control the scroll position, you need to add the code to handle it | 2022-11-03T12:27:18 | 2022-11-03T12:27:18 | {} | MEMBER |
vuejs | core | 1,303,353,567 | 7,022 | posva | Duplicate of https://github.com/vuejs/core/issues/4744 | 2022-11-04T12:06:36 | 2022-11-04T12:06:36 | {} | MEMBER |
vuejs | core | 1,298,459,433 | 7,004 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | d566a1aef74d23f930a5aecc9f3a2ea2fdb207d5 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-11-01T12:47:57 | 2022-11-08T05:37:21 | {} | NONE |
vuejs | core | 1,302,863,084 | 7,014 | zhangenming | > I can reproduce it. but I think this might be related to CSS rules. Could you reproduce it after removing all styles?
>
> > and more, if you Uncomment 59 line code `// r[2].part = '反';` this bug will disappear
>
> still can reproduce.
>
> if you remove `display: flex` rule of `body`. It will disappear.
do... | 2022-11-04T01:55:28 | 2022-11-04T01:55:28 | {} | CONTRIBUTOR |
vuejs | core | 1,304,283,974 | 7,027 | posva | I think codesandbox is using an outdated version of vue compiler. You should open an issue in Codesandbox repository | 2022-11-04T21:43:11 | 2022-11-04T21:43:11 | {} | MEMBER |
vuejs | core | 1,304,470,849 | 7,021 | ben-lau | I understand, but this situation should also be covered and paid attention to, a large number of frameworks are also used in this way. Using an array to store the instance covers this situation perfectly and doesn't cost a lot, poping and pushing performance is very fast, I think fix this will make Vue3 more robust. | 2022-11-05T10:12:05 | 2022-11-05T10:12:05 | {} | NONE |
vuejs | core | 1,304,950,586 | 7,017 | ben-lau | Actually, push is only called when currentInstance has a value, that means only in the case of the example and a small number of cases will occur. I know that is perf sensitive, but I feel like it should be fixed if it's a bug, so I hope to reconsider | 2022-11-07T00:38:40 | 2022-11-07T00:38:40 | {} | NONE |
vuejs | core | 1,305,653,410 | 3,951 | MajedMuhammad | >
@LinusBorg, Could you please clarify what can be in img() helper function? I couldn't see a way to resolve dynamic paths in either template or functions.
> I don't see a reason for a compiler feature here. This should be enough for most situations:
>
> ```js
> {
> template: `<img class="h-12" src="${img(... | 2022-11-07T13:57:11 | 2022-11-07T13:57:11 | {} | NONE |
vuejs | core | 1,305,933,428 | 7,051 | sxzz | I don't know... Maybe | 2022-11-07T17:14:32 | 2022-11-07T17:14:32 | {} | MEMBER |
vuejs | core | 1,301,690,266 | 7,014 | zhangenming | The result of both renderings is same and the height is exactly the same | 2022-11-03T06:16:19 | 2022-11-03T06:16:19 | {} | CONTRIBUTOR |
vuejs | core | 1,301,709,654 | 7,011 | zhangzhonghe | I think it is not a bug, because [here](https://stackblitz.com/edit/nuxt-starter-h98fpv?file=app.vue,InnerComponent.vue) is good. Maybe the playground had a bug.
I tried to start a playground server locally and also good:
<img width="1278" alt="image" src="https://user-images.githubusercontent.com/38434641/199663... | 2022-11-03T06:54:50 | 2022-11-03T07:06:31 | {} | MEMBER |
vuejs | core | 1,302,199,478 | 6,948 | edison1105 | in vue3
```html
<section id="hero" data-v-76d4cf95>
```
in vue2
```html
<section data-v-76d4cf95 id="hero">
```
This change will consistent with vue2.
LGTM. | 2022-11-03T14:27:58 | 2022-11-03T14:28:21 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,303,156,980 | 4,662 | abellion | As another workaround, here is how I got an entire application to be shipped as a custom element.
First, you need to disable your Vue components to be treated as custom elements (either by **not** turning on the `customElement` option of your bundler, or by **not** ending the name of your components by `.ce.vue`). ... | 2022-11-04T09:16:37 | 2022-11-04T09:18:13 | {} | NONE |
vuejs | core | 1,304,384,669 | 6,997 | edison1105 | @posva I believe there is a bug in the online sfc-playground because it works fine in my local sfc-playground.
> @webfansplz you are right, the problem happens with [an empty call](https://sfc.vuejs.org/#__SSR__eNp9kLtuwzAMRX+F0JIEiCV0dR0D3ToW6KrFdenYgfUARacoAv97qajI0AbZ+Lg4vJcX9RKjPi+oatWknqbIkJCXCHPnjwerOFnVWj+5GI... | 2022-11-05T02:51:19 | 2022-11-05T02:57:05 | {} | MEMBER |
vuejs | core | 1,304,850,924 | 7,039 | LinusBorg | Vue's reactivity will not trigger a svelte update/re-render. Without that, thr computed property will not be read again, so it wont be re-evaluated again.
I'll move this to discussions | 2022-11-06T17:24:09 | 2022-11-06T17:24:09 | {} | MEMBER |
vuejs | core | 1,304,894,878 | 7,017 | posva | > There are not many cases of using the stack, it is only used when the current stack needs to be suspended, not every time of mounting
Unfortunately, the push is called every time `setCurrentInstance()` is called, so it might be even more...
Keep in mind this is not about push being fast, it's about adding an ex... | 2022-11-06T21:11:35 | 2022-11-06T21:11:35 | {} | MEMBER |
vuejs | core | 1,304,899,786 | 7,035 | posva | Open a new issue if you manage to reproduce it. Thanks! | 2022-11-06T21:36:07 | 2022-11-06T21:36:07 | {} | MEMBER |
vuejs | core | 1,305,459,543 | 7,042 | zhangzhonghe | https://github.com/vuejs/core/blob/0841b9b5243acdaf191099b25e9a145b30189dea/packages/runtime-core/src/components/KeepAlive.ts#L306-L315
In this case, the ```shapeFlag``` of the modified component is marked as ```COMPONENT_KEPT_ALIVE``` because of the presence of the cache, causing the component not to be mounted:
... | 2022-11-07T11:18:05 | 2022-11-07T11:18:05 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,306,489,212 | 4,397 | lesonky | ```ts
const galleryDetailRef = ref<InstanceType<typeof GalleryDetail>>();
```
用 `InstanceType` 可以获取提示，但是和 defineExpose 没有联系，他会把组件所有的属性都获取出来 | 2022-11-08T01:38:10 | 2022-11-08T01:38:10 | {
"+1": 1,
"-1": 7
} | NONE |
vuejs | core | 1,306,684,246 | 6,804 | yyx990803 | Good job! | 2022-11-08T06:10:06 | 2022-11-08T06:10:06 | {} | MEMBER |
vuejs | core | 1,303,530,440 | 4,294 | Mon-ius | > @Mon-ius The entire discussion is about just that.
At least, I didn't see your solution at that time, event now none of them leads the final answer to enough simplicity.
What I put above could let the search engines matches the problems more explicitly leading guys here :) | 2022-11-04T13:19:08 | 2022-11-04T13:19:08 | {} | NONE |
vuejs | core | 1,304,303,130 | 7,003 | posva | This is a side effect of vue rendering again and setting the input value to the new value which have the trailing zeros stripped as it's a number.
I remember we discussed this kind of formatting requires handling with a string (so any trailing zero is kept) in userland but I think this could be improved too. At the ... | 2022-11-04T22:17:53 | 2022-11-04T22:19:49 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,304,471,892 | 7,003 | baiwusanyu-c | > This is a side effect of vue rendering again and setting the input value to the new value which have the trailing zeros stripped as it's a number.
>
> I remember we discussed this kind of formatting requires handling with a string (so any trailing zero is kept) in userland but I think this could be improved too. A... | 2022-11-05T10:12:54 | 2022-11-05T10:12:54 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,304,715,407 | 7,031 | edison1105 | > @edison1105 It seems to overlap with #6636 .
oh！I didnt notice that PR. | 2022-11-06T04:59:41 | 2022-11-06T04:59:41 | {} | MEMBER |
vuejs | core | 1,299,516,174 | 6,222 | try2020-code | same error | 2022-11-02T03:29:43 | 2022-11-02T03:29:43 | {} | NONE |
vuejs | core | 1,299,986,022 | 6,811 | adamjedlicka | @posva Hey. So I created a PR with a fix here: https://github.com/vuejs/core/pull/7009 . Could you please look at it and ideally merge it? | 2022-11-02T10:14:14 | 2022-11-02T10:14:14 | {} | CONTRIBUTOR |
vuejs | core | 1,300,025,366 | 6,997 | posva | The example on the docs is missing the serialization of the data. Without it, the client is not aware of the initial state when it renders and thus creates a Hydration mismatch. I would say this should be fixed in docs instead | 2022-11-02T10:46:37 | 2022-11-02T10:46:37 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,302,840,667 | 7,014 | zhangenming | VUE: https://stackblitz.com/edit/vitejs-vite-um8sx7?file=src%2FApp.vue&terminal=dev
react: https://stackblitz.com/edit/react-ts-shvbn3?file=style.css,App.tsx | 2022-11-04T01:09:59 | 2022-11-04T01:09:59 | {} | CONTRIBUTOR |
vuejs | core | 1,302,857,022 | 4,745 | yorickshan | > `[@vue/compiler-sfc] ::v-deep usage as a combinator has been deprecated. Use :deep(<inner-selector>) instead.`
>
> ```
> ::v-deep {
> .v-input--dense {}
> .v-skeleton-loader {}
> }
> ```
>
> I don't understand how to use :deep() for above scenario.
>
> can anyone help for the same?
hi, do you fin... | 2022-11-04T01:43:18 | 2022-11-04T01:43:18 | {
"eyes": 1
} | NONE |
vuejs | core | 1,305,046,161 | 6,248 | ChachaZhou | I have the same issue, when I updated Vite to `v3.3.2` and @vue/compiler-sfc to `v3.2.41`, it shows error like this:
`Error: [@vue/compiler-sfc] <script setup> cannot contain ES module exports. If you are using a previous version of <script setup>, please consult the updated RFC at https://github.com/vuejs/rfcs/pull/2... | 2022-11-07T03:56:24 | 2022-11-07T04:01:46 | {} | NONE |
vuejs | core | 1,305,738,883 | 7,048 | baiwusanyu-c | You can turn off `composite` to temporarily circumvent this problem 👀 | 2022-11-07T14:59:41 | 2022-11-07T14:59:41 | {} | MEMBER |
vuejs | core | 1,306,522,451 | 6,457 | yyx990803 | Previously the any casting was a hack to avoid the generated dts relying on `@babel/types`, but now it looks pointless since compiler-core also relies on `@babel/types`, and `@babel/types` is included as a dep of `@babel/parser` anyway. | 2022-11-08T02:15:28 | 2022-11-08T02:15:28 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,250,058,211 | 6,685 | theaungmyatmoe | Sorry, I just forgot the typescript version and to check the vite doc. I just fixed that bug by using type-only import that was introduced in typescript version 3.8.
https://www.typescriptlang.org/docs/handbook/release-notes/typescript-3-8.html#type-only-imports-and-export
```ts
import type {Session} from "@supa... | 2022-09-17T11:58:29 | 2022-09-17T11:58:29 | {} | NONE |
vuejs | core | 1,252,317,574 | 6,707 | LinusBorg | Mixing script setup and options API like this is invalid. We will make this fail in dev in a future release.
See a similar discussion in #6677 | 2022-09-20T12:57:59 | 2022-09-20T13:02:07 | {} | MEMBER |
vuejs | core | 1,253,070,112 | 2,084 | lifei110196 | 三年又三年 | 2022-09-21T01:00:43 | 2022-09-21T01:00:43 | {} | NONE |
vuejs | core | 1,253,218,208 | 5,623 | xiziliang | This conclusion can be reflected in the vuejs.org。because some people think shallowref data will not be updated. | 2022-09-21T05:19:46 | 2022-09-21T05:20:12 | {} | NONE |
vuejs | core | 1,254,936,651 | 6,420 | yangliguo7 | same problem。
But I found something even weirder
If you dont pass in a variable to `defineProps`, This property will not be undefined after `torefs`。
The code like
```
const props = defineProps({
form: {
type: Object,
required: true,
},
formOptions: {
type: Array as PropType<string[]>,
... | 2022-09-22T12:12:58 | 2022-09-22T12:12:58 | {
"rocket": 1
} | CONTRIBUTOR |
vuejs | core | 1,254,989,020 | 4,745 | Cyclodex | > So, I discover that `:deep(.class)` works the same as `::v-deep .class` BUT then... how can I do `::v-deep.class` (without spaces) with the new :deep() ?
Would that not be `.class:deep()` ? | 2022-09-22T12:59:40 | 2022-09-22T12:59:40 | {} | NONE |
vuejs | core | 1,256,401,747 | 6,732 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 188b108852e8e376619ee1b0b86088dc878e67ea |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-09-23T16:08:57 | 2022-09-23T16:08:57 | {} | NONE |
vuejs | core | 1,256,405,386 | 6,732 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 188b108852e8e376619ee1b0b86088dc878e67ea |
|<span aria-hidden="true">🔍</span> Latest deploy l... | 2022-09-23T16:12:48 | 2022-09-23T16:12:48 | {} | NONE |
vuejs | core | 1,250,031,386 | 6,685 | LinusBorg | This is not related to Vue core. My recommendation would be to join the Vite discord and ask the Vite community how do deal with this error.
https://discord.gg/4Hq8uzDy | 2022-09-17T08:49:02 | 2022-09-17T08:49:02 | {} | MEMBER |
vuejs | core | 1,250,034,073 | 6,669 | edison1105 | IMO, It does not make sense to execute emits in the effect function(computed,watch...). should avoid executing emits in effect functions | 2022-09-17T09:07:02 | 2022-09-17T09:09:12 | {} | MEMBER |
vuejs | core | 1,250,041,195 | 6,685 | theaungmyatmoe | Thanks I will do it | 2022-09-17T09:57:17 | 2022-09-17T09:57:17 | {} | NONE |
vuejs | core | 1,254,414,748 | 6,713 | zhangpaopao0609 | > duplicate #5770
>
> I don't think Vue should show a warning (even during development) if the value is not a string. It will probably just confuse people as to whether they can/cannot pass any type of value to the emit function.
That's right, this does cause such problems, thanks. I have removed that tip and le... | 2022-09-22T01:57:57 | 2022-09-22T01:58:51 | {} | NONE |
vuejs | core | 1,254,608,472 | 6,716 | posva | The static attribute takes precedence but you can inverse the order or specify the `.attr` modifier: https://sfc.vuejs.org/#eNp9kL1OxDAQhF9l2SYgXWLRhtxJdFS0NG5MspfLKf7R2glCUd6dde74EUhU9s6MvrF3wccQqnkirLGJLQ8hQaQ0hYN2gw2eEyzAdIQVjuwtFBIttNOu9S4msLGHffZviycaRw8vnsfuprh7+Ex0787YoX02lq5JjZZiND1pzLFGXWqlUIZENowmkUwAzen+sCxb... | 2022-09-22T06:57:33 | 2022-09-22T06:57:33 | {} | MEMBER |
vuejs | core | 1,254,612,854 | 6,711 | posva | Duplicate of https://github.com/vuejs/core/issues/5765 | 2022-09-22T07:02:56 | 2022-09-22T07:02:56 | {} | MEMBER |
vuejs | core | 1,255,081,902 | 4,294 | dparish | Will the fix for this get back ported to 2.7?
We keep our composables and components separate (makes testing VERY easy). It would make for much cleaner code if the prop type and emit types were declared in the composable file.
Example of what we do:
https://stackoverflow.com/questions/72890865/how-to-test-com... | 2022-09-22T14:10:17 | 2022-09-22T14:10:17 | {
"+1": 2
} | NONE |
vuejs | core | 1,250,034,340 | 6,669 | jacekkarczmarczyk | hm, why? I think that's a pretty common scenario | 2022-09-17T09:08:49 | 2022-09-17T09:08:49 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,250,034,827 | 6,669 | LittleSound | > IMO, It does not make sense to execute emits in the effect function(computed,watch...). should avoid executing emits in effect functions
I often write this way, and my code will often need to notify the parent components when the state changes. | 2022-09-17T09:12:05 | 2022-09-17T09:12:05 | {} | MEMBER |
vuejs | core | 1,250,073,443 | 6,669 | edison1105 | > I agree this is a bug, and I *think* it should be safe to pause tracking before emit() calls the handler. I sent a PR to discuss about
>
>
>
> @edison1105 What do you think?
Agreed | 2022-09-17T13:38:04 | 2022-09-17T13:38:04 | {} | MEMBER |
vuejs | core | 1,253,417,265 | 6,711 | zhangpaopao0609 | > I think you should change **$emit('update:modelValue', $event.target.value, {})** to **$emit('update:modelValue', $event.target.value)**, because in this scenario the third parameter is completely redundant.
>
> A warning should be triggered when the user sets a redundant parameter, while the redundant parameter c... | 2022-09-21T09:05:36 | 2022-09-21T11:03:40 | {} | NONE |
vuejs | core | 1,254,175,727 | 6,658 | sgpinkus | @Dedicatus546 @LinusBorg Added repro links. Also fixed typo in original issue: ~~3.2.28~~ -> 3.2.38 | 2022-09-21T20:08:23 | 2022-09-21T20:08:23 | {} | NONE |
vuejs | core | 1,256,408,563 | 6,732 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 188b108852e8e376619ee1b0b86088dc878e67ea |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2022-09-23T16:16:12 | 2022-09-23T16:16:12 | {} | NONE |
vuejs | core | 1,250,091,664 | 6,400 | LinusBorg | Because we need to transform it into a normal emits declaration during compilation:
```html
<script setup>
const emits = defineEmits(['someEvent'])
// setup code ...
</script>
```
essentially is compiled to this *during build*:
```js
export default defineComponent({
emits: ['someEvent'],
setup(_, {... | 2022-09-17T15:33:26 | 2022-09-17T15:33:26 | {} | MEMBER |
vuejs | core | 1,255,961,792 | 6,723 | LinusBorg | calling a slot function does *not* give you the same vnodes as the ones created while the slot is being rendered.
So `useSlots` cannot directly give you access to the *elements* created for a slot's vnodes. Please use Discord or the repo discussions to ask for help regarding your challenge. But this is not a bug. | 2022-09-23T09:00:36 | 2022-09-23T09:00:36 | {} | MEMBER |
vuejs | core | 1,250,006,949 | 6,669 | zhangzhonghe | > this is not related to emits. see [simpler demo](https://sfc.vuejs.org/#eNp9UbtuwzAM/BVCS23UsZM1cIJ2yNahQ0ctjkInTm1JoOgYReB/L/1IGrRAN/GOdyKPV/XqfXppUa1VHgxVniEgt36rbdV4RwxXICwT6Ao2p11ZomHooSTXwJPonrTV1jgbGIxrfI2MB9gMkqgs6oDxjW3CccZXgmn74BcV4csaiGLYbOGqLUBVRne39FLULcYjDvKJDa7GtHbHSCxncuA0F11RMVjs4F3GqwJGNDjKPh9Vg67liB... | 2022-09-17T05:49:04 | 2022-09-17T05:49:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,250,062,414 | 6,400 | jez9999 | @sxzz I don't use TypeScript, I hate it. You can't just assume everyone's using TypeScript. | 2022-09-17T12:26:04 | 2022-09-17T12:26:04 | {
"eyes": 1
} | NONE |
vuejs | core | 1,251,127,656 | 6,699 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 5790adf7b2f5ebe9bbad9bb96b9f59d468be7f0d |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-09-19T14:47:47 | 2022-09-19T20:46:44 | {} | NONE |
vuejs | core | 1,254,114,467 | 6,651 | shigma | @edison1105 I opened #6660. Is there any hope that we can get it in a future version? | 2022-09-21T19:06:29 | 2022-09-21T19:06:29 | {} | CONTRIBUTOR |
vuejs | core | 1,254,663,949 | 6,658 | sgpinkus | @posva yeah wasn't the best, was a work in progress. Wasn't sure where to start so started from prod app and cut off all cruft I could think of in time I had. Was planning to investigate further then revise. It does however reliably trigger the error.
Your correct most of the issues listed by @AlvaroBrasilia seem to... | 2022-09-22T07:58:17 | 2022-09-22T07:59:53 | {} | NONE |
vuejs | core | 1,255,127,272 | 6,718 | LinusBorg | please open an issue in this repo for vue-tsc/volar:
https://github.com/johnsoncodehk/volar
| 2022-09-22T14:40:54 | 2022-09-22T14:40:54 | {} | MEMBER |
vuejs | core | 1,250,049,340 | 6,661 | LinusBorg | closing as duplicate pf #6631 | 2022-09-17T10:55:00 | 2022-09-17T10:55:00 | {} | MEMBER |
vuejs | core | 1,250,563,618 | 6,690 | yuanxin518 | ```
const nameObjList = computed(()=>{
return users.map((name)=>name.split(" "))
})
```
It seems you could use `computed` function instead of it，if use `v-const...` it may also take up more memory. | 2022-09-19T04:41:29 | 2022-09-19T04:45:07 | {
"heart": 2
} | NONE |
vuejs | core | 1,252,000,407 | 6,697 | sishen654 | modify your demo, look like more directly :
https://sfc.vuejs.org/#__DEV__eNp9Uj1v2zAQ/SsHLpYBiWziqa5spEO3dinQqeygSmeXLb9AUsog6L/3SMWOkwBZhPt67x3vaWafvefTiGzP2tgH5RNETKMH3dnzQbIUJTtKq4x3IcEMAU81OPvNjTbhUEPvjB9LNGGIytna2R9+6KgEC5yCM7Ah+o200vbOxgRa0eeQiaqfdzXc17D7tX1uq4TmO57iZWTtXRWraguHI8zSAgyuHw3axLth+DJR8JWo0WKoNt... | 2022-09-20T08:15:28 | 2022-09-20T08:15:28 | {} | NONE |
vuejs | core | 1,252,321,646 | 6,706 | LinusBorg | this is not a problem for Vue core. | 2022-09-20T13:01:22 | 2022-09-20T13:01:22 | {
"eyes": 1
} | MEMBER |
vuejs | core | 1,253,643,252 | 4,915 | ismailthasreef | onVnodeUnmounted=fn<onVnodeUnmounted> ref=Ref< undefined | 2022-09-21T12:33:01 | 2022-09-21T12:33:01 | {} | NONE |
vuejs | core | 1,254,766,772 | 6,658 | sgpinkus | @posva Made repro much simpler. Hope that helps. Still using Vuetify because the source of the error here and in most of the other issues is in some (weird, but still valid Vue) stuff VImg is doing onBeforeMount -- https://github.com/vuetifyjs/vuetify/blob/faf66716e6b41cbecb89de562bcc4d73b3009c8c/packages/vuetify/src/... | 2022-09-22T09:28:40 | 2022-09-22T09:28:40 | {} | NONE |
vuejs | core | 1,255,958,426 | 6,724 | LinusBorg | > If this is caused by variables, why use a new_ Data can be modified directly and rendered normally?
I'm not sure what you mean here. | 2022-09-23T08:57:01 | 2022-09-23T08:57:15 | {} | MEMBER |
vuejs | core | 1,250,115,271 | 4,067 | LinusBorg | seems fixed | 2022-09-17T17:59:03 | 2022-09-17T17:59:03 | {} | MEMBER |
vuejs | core | 1,253,408,839 | 6,697 | simonefranza | With the composition API it does not work either in production or development. [See here](https://sfc.vuejs.org/#__DEV__eNp9UsFu2zAM/RVCGFAHsKW0OS1ziu6ww4Cddp128Cwm1SZLgiS7Awz/+2jZbrtsKBAgJB/1Hs3HkX30ng89siOrYxu0T2AaezlJlqJk99Lib+9CAoXnpjcJRmkBVJOaYrfEAAFTH+yWARgdExzh220JdyUcvpcbEPCMAW2LkWCwvTErNM1/EyUyda63CdXGLpNybd+h... | 2022-09-21T08:58:06 | 2022-09-21T08:58:06 | {
"+1": 1
} | NONE |
vuejs | core | 1,253,438,075 | 6,697 | simonefranza | As a temporary fix, you can create a watcher on the list, then `await nextTick()`, temporary set the references to `[]` and finally store the references back into the array. Like this
```
watch(list.value, async () => {
await nextTick();
const temp = itemRefs.value;
itemRefs.value = [];
itemRefs.value = t... | 2022-09-21T09:21:56 | 2022-09-21T09:21:56 | {
"+1": 2
} | NONE |
vuejs | core | 1,253,458,409 | 6,707 | segevfiner | Yeah. And using them via splatting saves from needing to make a mixin shim for the old code that uses them. Thanks! | 2022-09-21T09:40:24 | 2022-09-21T09:40:24 | {} | NONE |
vuejs | core | 1,250,053,992 | 6,271 | posva | This is expected: you are responsible for cleaning up manually added DOM | 2022-09-17T11:26:56 | 2022-09-17T11:26:56 | {} | MEMBER |
vuejs | core | 1,250,980,982 | 6,697 | simonefranza | ~~I don't know... the order is not really the problem here. The source and the ref array are somehow different.~~ The change does also not appear inside a watcher.
Like with the clicks, the watcher works fine in production, but in development, it's like if the updated is not sent to the UI and the watcher
Edit: th... | 2022-09-19T12:53:51 | 2022-09-19T12:58:35 | {} | NONE |
vuejs | core | 1,251,794,198 | 6,222 | xinsites |
> > @midfar 看下这个能不能用 [#4339 (comment)](https://github.com/vuejs/core/pull/4339#issuecomment-1238984279)
> > 自己给 keep-alive 包裹的 component 包个壳。 我原本在做做多tab单页应用的时候，也遇到这个问题，加了这个壳后，在开发和生产模式下都没有再出现过这个问题。
>
> 你这样改貌似可以，但是控制台有另一个警告（好像不影响功能） [Vue warn]: Vue received a Component which was made a reactive object. This c... | 2022-09-20T03:34:51 | 2022-09-20T03:34:51 | {} | NONE |
vuejs | core | 1,252,815,205 | 6,707 | LinusBorg | you *can* use a normal setup() function, if that helps. | 2022-09-20T19:33:18 | 2022-09-20T19:33:18 | {} | MEMBER |
vuejs | core | 1,256,028,614 | 6,728 | deot | A new problem after #6614 fixed | 2022-09-23T10:12:14 | 2022-09-23T10:12:14 | {} | NONE |
vuejs | core | 1,250,031,739 | 6,672 | LinusBorg | the slot props are undefined because you call the slot's function without an argument on line 35.
I recommend to ask in the repo discussions or the Vue discord server for help on how to achieve your desired behavior. | 2022-09-17T08:52:04 | 2022-09-17T08:52:04 | {} | MEMBER |
vuejs | core | 1,250,031,860 | 6,669 | edison1105 | > > this is not related to emits. see [simpler demo](https://sfc.vuejs.org/#eNp9UbtuwzAM/BVCS23UsZM1cIJ2yNahQ0ctjkInTm1JoOgYReB/L/1IGrRAN/GOdyKPV/XqfXppUa1VHgxVniEgt36rbdV4RwxXICwT6Ao2p11ZomHooSTXwJPonrTV1jgbGIxrfI2MB9gMkqgs6oDxjW3CccZXgmn74BcV4csaiGLYbOGqLUBVRne39FLULcYjDvKJDa7GtHbHSCxncuA0F11RMVjs4F3GqwJGNDjKPh9Vg67l... | 2022-09-17T08:52:54 | 2022-09-17T08:52:54 | {} | MEMBER |
vuejs | core | 1,250,070,219 | 6,400 | LinusBorg | I get your perspective. And I would be cool with supporting this if we could make it work in a way that would not degrade DX like props inference in the template (for TS and JS users alike).
That's a big if though, because it would need some serious additional complexity in the compiler, which would now need to rea... | 2022-09-17T13:17:42 | 2022-09-17T13:17:42 | {} | MEMBER |
vuejs | core | 1,250,071,215 | 6,400 | jez9999 | How come emits are dealt with as a macro and not an imported function, out of interest? | 2022-09-17T13:24:19 | 2022-09-17T13:24:19 | {} | NONE |
vuejs | core | 1,250,208,674 | 6,400 | Asylian21 | > I'm not really convinced this would be a good idea as well.
>
> > @sxzz I don't use TypeScript, I hate it. You can't just assume everyone's using TypeScript.
>
> instead of the prop Type you could expose the props object as a separate export.
>
> ```js
> // hooks.js
> export const useComposableProps = {
>... | 2022-09-18T07:15:52 | 2022-09-18T07:15:52 | {} | NONE |
vuejs | core | 1,250,411,761 | 6,693 | theaungmyatmoe | So, it seem works when I console log the array. But still not working in Vue dev tool. Vue dev tool must be reactive. It's bug of devtool. | 2022-09-18T23:37:32 | 2022-09-18T23:37:32 | {} | NONE |
vuejs | core | 1,250,430,160 | 6,693 | edison1105 | > So, it seem works when I console log the array. But still not working in Vue dev tool. Vue dev tool must be reactive. It's bug of devtool.
you should move this issue to https://github.com/vuejs/devtools
| 2022-09-19T00:49:47 | 2022-09-19T00:49:47 | {} | MEMBER |
vuejs | core | 1,251,088,666 | 6,690 | tachibana-shin | > ```
> const nameObjList = computed(()=>{
> return users.map((name)=>name.split(" "))
> })
> ```
>
> It seems you could use function instead of it，if use it may also take up more memory.`computed``v-const...`
This is memory-intensive and I need v-tools for more complex functions. I don't always need to c... | 2022-09-19T14:18:39 | 2022-09-19T14:18:39 | {} | NONE |
vuejs | core | 1,252,455,179 | 4,294 | underdoeg | > Any progress on a real fix for this issue?
AFAIK this is on the roadmap for the vue 3.3 release | 2022-09-20T14:39:25 | 2022-09-20T14:39:25 | {
"+1": 2
} | NONE |
vuejs | core | 1,252,657,477 | 6,704 | LinusBorg | O think the actual issue that for A.vue, the compiler misses to add a name property, and you can only use `include/exclude` on components that have an explicit name set.
for `script setup`, the compiler usually uses the file name, but that fails to happen for an empty script-setup block. | 2022-09-20T17:13:30 | 2022-09-20T17:34:33 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,252,769,764 | 6,707 | segevfiner | A lint can also help, but might be a bit complex? Oh well, this will make migration difficult for us due to widespread use of mixins that are difficult to convert. Any suggestions on how to ease migration if such dual usage should not be done? | 2022-09-20T18:45:57 | 2022-09-20T19:55:59 | {} | NONE |
vuejs | core | 1,253,396,108 | 6,697 | baiwusanyu-c | I also think this is a bug. When the list changes and the update is triggered, toDisplayString will be called. At this time, the dom has not changed, so the itemRefs value is still 3 divs, and then the converted string is the same as before the update. When comparing dynamicchildren , no updates were made. Also I found... | 2022-09-21T08:46:55 | 2022-09-21T08:49:49 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,253,762,205 | 6,711 | sqal | @zhangpaopao0609 duplicate https://github.com/vuejs/core/issues/5765 | 2022-09-21T14:05:14 | 2022-09-21T14:05:14 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,250,032,929 | 6,669 | LittleSound | I know the concept you are talking about, but the issue I want to discuss now has nothing to do with recursion.
The topic of this issue is questioning about whether `watchEffect` should listen for responses in the `emits` event subscriber function. | 2022-09-17T09:01:01 | 2022-09-17T09:01:01 | {} | MEMBER |
vuejs | core | 1,250,049,016 | 6,670 | LinusBorg | it seems your setup is using an eslint rule meant for Vue 2 - in Vue 2, template wrappers in v-for cannot be keyed.
https://eslint.vuejs.org/rules/no-v-for-template-key.html#vue-no-v-for-template-key
In Vue 3, they can (and should), which is covered by this rule:
https://eslint.vuejs.org/rules/no-v-for-templa... | 2022-09-17T10:52:34 | 2022-09-17T10:52:34 | {} | MEMBER |
vuejs | core | 1,250,062,841 | 6,400 | LinusBorg | I'm not really convinced this would be a good idea as well.
> @sxzz I don't use TypeScript, I hate it. You can't just assume everyone's using TypeScript.
instead of the prop Type you could expose the props object as a separate export.
```js
// hooks.js
export const useComposableProps = {
foo: String
}
... | 2022-09-17T12:29:24 | 2022-09-17T12:29:24 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,250,279,072 | 6,691 | LinusBorg | > The function receives the **raw** props **received by the component** as the argument.
it receives the props they way there were passed from the parent - in which `c` was undefined. | 2022-09-18T13:23:26 | 2022-09-18T13:23:26 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.