Datasets:
open-index
/
open-github-issues

Dataset card Data Studio Files
xet
 Community
1
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,252,578,590
6,704
moushicheng
Change A.vue to look like the following ```vue <template > <input type="text" placeholder="This is A " :value="value"> </template> <script setup lang="ts"> import {shallowRef} from "vue" const value=shallowRef('') </script> ``` it can cache。 why？i guess beacuse KeepAlive saves VNodes but not Dom ...
2022-09-20T16:07:23
2022-09-21T00:04:44
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
1,253,144,436
6,710
Justineo
This isn't really a problem of Vue. In your case `￥` is produced by the input method. The `keyup` event shows you which key is pressed, not which character you end up inputing.
2022-09-21T02:57:15
2022-09-21T02:57:15
{}
MEMBER
vuejs
core
1,253,281,794
6,102
techbirds
hi @yyx990803, Do you have time to help review this pr?
2022-09-21T06:53:12
2022-09-21T06:53:12
{}
NONE
vuejs
core
1,253,781,055
6,713
sqal
duplicate https://github.com/vuejs/core/pull/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.
2022-09-21T14:18:48
2022-09-21T14:18:48
{ "+1": 2 }
CONTRIBUTOR
vuejs
core
1,254,607,911
6,716
posva
Duplicate of https://github.com/vuejs/core/issues/2059
2022-09-22T06:56:51
2022-09-22T06:56:51
{}
MEMBER
vuejs
core
1,255,128,795
6,707
LinusBorg
I'll close this in favor of #6677 which tracks the underlying issue.
2022-09-22T14:41:58
2022-09-22T14:41:58
{}
MEMBER
vuejs
core
1,255,305,267
6,716
xavier83ar
Cool, thank you @posva and sorry for the duplicated issue, I searched before creating it, but I was searching wrong, I thought it only affected inputs...
2022-09-22T17:01:51
2022-09-22T17:01:51
{}
NONE
vuejs
core
1,255,963,197
6,724
huifer
When I execute the click2 method, I render normally. I don't want to render in this way. I want to render directly by reassigning a
2022-09-23T09:02:13
2022-09-23T09:02:13
{}
NONE
vuejs
core
1,255,972,050
6,463
jiangmaniu
Same error, what's the progress?
2022-09-23T09:11:19
2022-09-23T09:11:19
{}
NONE
vuejs
core
1,256,102,573
5,612
cefn
Update: We are still battling with being unable to consistently establish the props of components in our test suites. Is there an option I've missed somewhere? Within a test we need to be able to author functions that take multiple different components. For example, our components often need to be tested as a d...
2022-09-23T11:37:45
2022-09-23T11:37:45
{}
NONE
vuejs
core
1,250,210,309
6,389
jacekkarczmarczyk
Issue seems to be fixed in latest Vue 2 (probably https://github.com/vuejs/vue/commit/f0057b101e6451d5095cdb7fd6308fd31ac0450c / https://github.com/vuejs/vue/issues/12703) and Vue 3 (probably https://github.com/vuejs/core/commit/78c199d6dbe8931520b75d8bfe0d49366a06922a / https://github.com/vuejs/core/issues/2291)
2022-09-18T07:27:45
2022-09-18T07:27:45
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
1,250,794,949
6,695
LinusBorg
The toggle event will necessarily trigger on both, because when one opens, the other closes - and both of these changes trigger a `toggle` event. This is not a Vue bug, So I'll turn this into a discussion thread.
2022-09-19T09:39:12
2022-09-19T09:39:12
{}
MEMBER
vuejs
core
1,251,094,175
6,690
tachibana-shin
I can solve this problem with a blank variable like this: ```vue <template> <div v-for="name in users" :key="name" v-empty-direactive="tmp = name.split(' ')"> First name: {{ tmp[0] }} <br> Last name: {{ tmp[1] }} </div> </template> ``` then `vue/compiler` would understand `tmp` as a `tmp` and would...
2022-09-19T14:22:42
2022-09-19T14:22:42
{}
NONE
vuejs
core
1,253,601,367
5,670
ealldy
Any updates on this?
2022-09-21T11:55:42
2022-09-21T11:55:42
{}
NONE
vuejs
core
1,254,391,732
4,745
bestime
> The new syntax require using `:deep` (or `::v-deep`) as a **pseudo function** - i.e. the parens are required: > > ```js > :deep {} /* this is wrong */ > > :deep(div) {} /* this is correct */ > ``` > > Without parens you are using it as a **combinator**, which is exactly what the message is warning you abou...
2022-09-22T01:20:54
2022-09-22T01:20:54
{ "eyes": 3 }
NONE
vuejs
core
1,254,588,427
5,400
caozhong1996
> Hi buddy, I need to confirm whether #5363 #5400 already been fixed and already been merged to main branch, because I could not find it been mentioned in changelog. Very much appreciated if you can reply me ASAP, thanks. Nope, it's related to the weird behavior of chrome🙈
2022-09-22T06:32:01
2022-09-22T06:32:01
{}
CONTRIBUTOR
vuejs
core
1,254,956,055
6,420
LinusBorg
> This type will not be infer to undefined because you set `required: true`
2022-09-22T12:30:23
2022-09-22T12:30:23
{}
MEMBER
vuejs
core
1,255,304,543
6,420
LinusBorg
```ts const aaa = { form: { type: Object, required: true, }, formOptions: { type: Array as PropType<FormOptionItem[]>, required: true, }, } as const ``` without `as const`, TS will infer the `required` prop as `boolean`, meaning it could be true *or* false.
2022-09-22T17:01:06
2022-09-22T17:01:06
{}
MEMBER
vuejs
core
1,255,946,005
6,724
huifer
If this is caused by variables, why use a new_ Data can be modified directly and rendered normally? I try to use the following code to try, but I can't render normally ``` <template> <div> <p>{{ a.old_data }}</p> <button @click="click">渲染</button> <p>{{ a.new_data }}</p> </div> </template> <...
2022-09-23T08:43:40
2022-09-23T08:43:40
{}
NONE
vuejs
core
1,250,064,468
6,400
jez9999
2. the whole point, I think, is that there are some composables the *whole point of which* is to extract out the event emitting logic, so you'd only use it if you did want to opt in to that. As for the other stuff, well it's all subjective. You're weakening the value proposition of composables IMHO. Kind of sucks th...
2022-09-17T12:40:52
2022-09-17T12:50:47
{}
NONE
vuejs
core
1,250,870,770
6,697
simonefranza
Sorry, missclicked
2022-09-19T11:01:35
2022-09-19T11:01:35
{}
NONE
vuejs
core
1,252,002,273
6,697
sishen654
> modify your demo, look like more directly : > > https://sfc.vuejs.org/#__DEV__eNp9Uj1v2zAQ/SsHLpYBiWziqa5spEO3dinQqeygSmeXLb9AUsog6L/3SMWOkwBZhPt67x3vaWafvefTiGzP2tgH5RNETKMH3dnzQbIUJTtKq4x3IcEMAU81OPvNjTbhUEPvjB9LNGGIytna2R9+6KgEC5yCM7Ah+o200vbOxgRa0eeQiaqfdzXc17D7tX1uq4TmO57iZWTtXRWraguHI8zSAgyuHw3axLth+DJR8JWo0...
2022-09-20T08:17:13
2022-09-20T08:17:13
{ "+1": 4 }
NONE
vuejs
core
1,254,609,871
6,658
posva
Your reproduction is not minimal, please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro when reporting a bug. Most bugs should be reproducible with the [SFC Playground](https://sfc.vuejs.org). There seems to be other duplicates as pointed out by @AlvaroBrasilia in https://github.com/vuejs...
2022-09-22T06:59:21
2022-09-22T06:59:21
{}
MEMBER
vuejs
core
1,254,951,086
6,715
zhangzhonghe
I found that this is because the SSR side allows comment nodes in the TransitionGroup, while on the client side it skips the rendering of comment nodes, so it causes a mismatch warning during hydration. Here is the source code snippet that skips the rendering of comment nodes: https://github.com/vuejs/core/blob/5...
2022-09-22T12:26:18
2022-09-22T12:26:18
{ "+1": 1 }
MEMBER
vuejs
core
1,250,040,793
6,669
LinusBorg
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?
2022-09-17T09:54:17
2022-09-17T09:54:17
{ "heart": 2 }
MEMBER
vuejs
core
1,252,849,549
6,707
segevfiner
That will help. Although `script setup` is obviously nicer... Sadly I doubt mixins can be used or will be made available to use with it, as they are "technically deprecated"/"not recommended", so guess that's our only option for the time being.
2022-09-20T20:05:25
2022-09-20T20:05:25
{}
NONE
vuejs
core
1,252,878,293
6,707
LinusBorg
You'll need to convert the mixins sometime, as you can't use mixins in Composition API, yes. I'd likely try and convert one mixin into a composable, then inject that via `setup`: ```js // use it just for composables from mixins setup() { return { ...useMyComposableFromAMixin() } }, // rest of existing...
2022-09-20T20:29:57
2022-09-20T20:29:57
{}
MEMBER
vuejs
core
1,255,924,969
6,724
LinusBorg
reassigning *variables *is never reactive, this is a limitation in Javascript. And the reason why `ref()` exists.
2022-09-23T08:20:56
2022-09-23T08:20:56
{}
MEMBER
vuejs
core
1,250,987,234
6,698
LinusBorg
https://v3-migration.vuejs.org/breaking-changes/transition-as-root.html
2022-09-19T12:59:35
2022-09-19T12:59:35
{}
MEMBER
vuejs
core
1,253,330,786
6,711
zhangzhonghe
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 can sim...
2022-09-21T07:45:32
2022-09-21T07:45:32
{}
MEMBER
vuejs
core
1,254,351,677
6,716
xavier83ar
I want to add a bit more context, because at a first glance it doesn't make any sense to add both `name` and `:name` attributes to input element. I'm using vue within a php framework, which is the responsible for rendering input elements, like this: ```php <?= $this->Form->hidden('horarios.hora_inicio', [ '...
2022-09-22T00:06:22
2022-09-22T02:14:44
{}
NONE
vuejs
core
1,254,577,667
6,706
ihardz
Okay, https://github.com/vuejs/create-vue/issues/165
2022-09-22T06:18:55
2022-09-22T06:18:55
{}
NONE
vuejs
core
1,254,465,460
6,713
zhangzhonghe
> > 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...
2022-09-22T03:12:56
2022-09-22T03:12:56
{}
MEMBER
vuejs
core
1,250,056,212
6,596
LinusBorg
Can't reproduce the problem when following the instructions. I get exactly one console error&warning as would be expected. <img width="1152" alt="Bildschirmfoto 2022-09-17 um 13 35 59" src="https://user-images.githubusercontent.com/1444526/190854606-abb6280a-3f01-444f-bb11-42e1cef5f11f.png">
2022-09-17T11:42:57
2022-09-17T11:42:57
{}
MEMBER
vuejs
core
1,250,061,572
6,684
LinusBorg
duplicate of #6400
2022-09-17T12:19:52
2022-09-17T12:19:52
{}
MEMBER
vuejs
core
1,250,060,745
6,422
LinusBorg
Hi! so the immediate fix is simple: ```diff const props = withDefaults(defineProps<Props>(), { message: "This icon was defaulted inside of the component, and is missing the required 'data-v-' attribute for scoped styling", - icon: ChatIcon, + icon: () => ChatIcon, }); ``` 1. These icons are fun...
2022-09-17T12:14:46
2022-09-17T17:54:08
{ "+1": 1 }
MEMBER
vuejs
core
1,254,416,263
5,400
ajesses
Hi buddy, I need to confirm whether #5363 #5400 already been fixed and already been merged to main branch, because I could not find it been mentioned in changelog. Very much appreciated if you can reply me ASAP, thanks.
2022-09-22T01:59:48
2022-09-22T01:59:48
{}
NONE
vuejs
core
1,254,960,684
6,420
yangliguo7
> > This type will not be infer to undefined > > because you set `required: true` but . if I code like this。the type will be undefined ``` const aaa = { form: { type: Object, required: true, }, formOptions: { type: Array as PropType<FormOptionItem[]>, required: true, }, } co...
2022-09-22T12:34:44
2022-09-22T12:34:44
{}
CONTRIBUTOR
vuejs
core
1,157,500,908
6,063
liulinboyi
In the file `vite.config.js` remove the `whitespace: 'preserve'` it will be fine. [Doc](https://vuejs.org/api/application.html#app-compileroptions-whitespace) ```javascript import { defineConfig } from 'vite' import vue from '@vitejs/plugin-vue' // https://vitejs.dev/config/ export default defineConfig({ p...
2022-06-16T10:29:18
2022-06-16T10:29:18
{}
MEMBER
vuejs
core
1,159,163,926
6,134
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | 9c1e34dca3d3fc44be01bffed5f6370f09265033 | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2022-06-17T19:17:27
2022-06-17T19:17:27
{}
NONE
vuejs
core
1,159,209,162
6,130
nros
Maybe I have not understood the concept of a writable computed value. The documentation is not very clear about it. Its example uses non reactive storing of the data as well. What is the use case then? https://vuejs.org/guide/essentials/computed.html#writable-computed I can use a ref as storage to make it reacti...
2022-06-17T20:32:44
2022-06-17T20:32:44
{}
NONE
vuejs
core
1,159,468,713
4,662
Daniel-Knights
If there aren't any plans to fix this soon, it really needs to be mentioned in the docs.
2022-06-18T13:50:54
2022-06-18T13:50:54
{ "+1": 18 }
NONE
vuejs
core
1,159,486,782
4,294
jblachly
Because I ran into this problem* today, but with `defineEmits`, I am boosting the search-engine signal for defineEmits as this seems to be the overarching issue tracking a single solution for both. *to clarify, like others I've tried to extract Type literals for use in `defineProps` and `defineEmits` from a set of r...
2022-06-18T15:47:34
2022-06-18T15:47:34
{}
NONE
vuejs
core
1,160,105,965
6,143
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | 188254d9e2caaa17ec406154526c3348d6bca3b9 | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2022-06-20T08:00:51
2022-06-20T08:00:51
{}
NONE
vuejs
core
1,162,522,258
6,157
xenyou
Got it. Thanks.
2022-06-22T01:29:29
2022-06-22T01:29:29
{}
NONE
vuejs
core
1,164,648,541
6,164
makkarpov
Looks like it's literally just a two-line patch, since filename is already passed to the compiler, but just excluded from the context for some reason: ```diff diff --git a/packages/compiler-core/src/transform.ts b/packages/compiler-core/src/transform.ts index 6397df92..ce6091d3 100644 --- a/packages/compiler-core...
2022-06-23T16:53:08
2022-06-23T16:53:08
{}
NONE
vuejs
core
1,157,206,956
6,120
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | d81253fbf7c41c399cb831e1d5acff4d369b9f40 | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2022-06-16T04:04:03
2022-06-16T04:04:03
{}
NONE
vuejs
core
1,157,215,261
6,120
leopiccionia
Have you tested if this works? It looks like it may throw a `ReferenceError`.
2022-06-16T04:20:53
2022-06-16T04:20:53
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
1,157,790,049
2,636
diveDylan
> I'd rather say that `<p> test </p>` is expected, because the text (`test`) exists in a new line: > > ``` > <HelloWorld msg="Hello Vue 3 in CodeSandbox!"> > <template #test> > test > </template> > test > </HelloWorld> > ``` > > To meet your expectations, you can remove newline like...
2022-06-16T15:22:38
2022-06-16T15:23:36
{}
NONE
vuejs
core
1,158,754,538
4,344
cheny-github
nice dude
2022-06-17T10:55:08
2022-06-17T10:55:08
{}
NONE
vuejs
core
1,159,444,835
6,049
LinusBorg
Well, read the warning and act accordingly: a) switch away from setup async to normal setup, or b) add a Suspense boundary.
2022-06-18T11:02:11
2022-06-18T11:02:11
{}
MEMBER
vuejs
core
1,161,302,214
5,242
emarbo
Hi there, sorry for the late reply. I have updated the [demo project](https://github.com/emarbo/nested-teleport-demo) to the latest Vue version and changed from `body` to `#body-teleports` and everything worked as expected. Thanks for the fix!
2022-06-21T06:03:32
2022-06-21T06:03:32
{}
NONE
vuejs
core
1,162,519,795
6,131
yyx990803
Looks like Vue's usage should be supported in 61, but I'll need more info to see what's going on. Is there any error thrown or is it just silently ignored?
2022-06-22T01:24:17
2022-06-22T01:24:17
{}
MEMBER
vuejs
core
1,162,595,971
6,026
iwusong
ERROR: type should be string, got " https://staging-cn.vuejs.org/api/application.html#app-config-compileroptions \r\n\r\ncomments need final rendering on dom"
2022-06-22T03:29:20
2022-06-22T03:29:20
{}
CONTRIBUTOR
vuejs
core
1,164,812,548
5,746
LinusBorg
This happens because of tree shaking. Rollup/Vite removes the default export, as is never imported anywhere. and the main export, generated by the `@vite/plugin-vue` plugin, does something like this: ```js export default /* @__PURE__ */ _export_sfc(_sfc_main$1, [["render", _sfc_render]]); ``` This is useful fo...
2022-06-23T19:57:59
2022-06-23T19:59:30
{}
MEMBER
vuejs
core
1,155,484,446
2,291
zenflow
> As a workaround, use a post flush watcher: > > ```js > watch: { > "$route.params.fooId": { > handler: "fetch", > flush: "post" > } > } > ``` @yyx990803 Does `flush: "post"` restore vue2 behavior? Or how does that compare to vue2 behavior? I can't find much documentation on this breaking chang...
2022-06-14T17:18:48
2022-06-14T17:18:48
{ "hooray": 1 }
NONE
vuejs
core
1,156,368,010
6,112
mivui
I have tested
2022-06-15T11:43:22
2022-06-15T11:43:22
{}
NONE
vuejs
core
1,158,418,219
5,712
zz541843
> 我不是显示有问题，我显示也正确，我是把这ts文件编译一份.d.ts文件报错了
2022-06-17T02:29:30
2022-06-17T02:29:30
{}
NONE
vuejs
core
1,159,334,297
6,049
BeginnerDone
have the same problem
2022-06-18T01:38:27
2022-06-18T01:38:27
{}
NONE
vuejs
core
1,159,744,167
6,031
Barrierml
> I think the documentation should mention gotchas such as `v-if` not working on `template` elements and that `v-if` and `v-for` cannot be used together on the same element. > > I have not tried using a class or style to accomplish any of this. > > The behavior of undefined properties on an object being rendered ...
2022-06-19T14:39:17
2022-06-19T14:39:17
{}
NONE
vuejs
core
1,163,037,272
5,746
gwen1230
Same here
2022-06-22T12:29:40
2022-06-22T12:29:40
{}
NONE
vuejs
core
1,155,893,188
6,111
xi2And33
> It can be solved in userland with a computed property and a deep-merging function (e.g. [defu](https://www.npmjs.com/package/defu)). it is solved my problem already tks. but i need to import new lib defu , althought it is worked , but need to define a new variable. what if we handle this logic in props? maybe we...
2022-06-15T02:03:22
2022-06-15T02:03:22
{}
NONE
vuejs
core
1,155,071,344
3,933
danielSt-dev
Hi, we updated our app to vue 3.2.37 and the workaround didn't work anymore. It is because of merge #5944 (vue version 3.2.36). the call to performance.now through a function is replaced by a direct function assignment, so we can not override the performance.now anymore. Current solution is downgrade to vue 3.2...
2022-06-14T11:41:25
2022-06-15T08:18:20
{}
NONE
vuejs
core
1,156,403,021
5,435
BigLiao
Works for me. Is there any progress?
2022-06-15T12:22:09
2022-06-15T12:22:09
{}
NONE
vuejs
core
1,158,419,549
5,712
kikyouink
> > > > 我不是显示有问题，我显示也正确，我是把这ts文件编译一份.d.ts文件报错了 那我就不清楚了。。。
2022-06-17T02:31:36
2022-06-17T02:31:36
{}
NONE
vuejs
core
1,159,224,613
6,130
nros
You might be correct that notifying all the deps is not following the concept of computed-refs. Nevertheless I think you have missed the consequence of the current implementation, that the following fundamental concept of computer languages does not hold true anymore? Maybe I am missing your point, but please re-con...
2022-06-17T21:02:38
2022-06-17T21:09:53
{}
NONE
vuejs
core
1,159,552,295
6,049
johnsoncodehk
The problem occurs in a bit of complex code, I'll try to update the example to exclude `defineComponent({ async setup() { } });`.
2022-06-18T20:07:12
2022-06-18T20:07:12
{}
MEMBER
vuejs
core
1,159,730,052
6,031
vanillajonathan
I think the documentation should mention gotchas such as `v-if` not working on `template` elements and that `v-if` and `v-for` cannot be used together on the same element. I have not tried using a class or style to accomplish any of this. The behavior of undefined properties on an object being rendered as the str...
2022-06-19T13:41:19
2022-06-19T13:41:19
{}
NONE
vuejs
core
1,162,476,854
6,157
xenyou
I just noticed it's not reproduced in another machine. M1 mac has some issue? System: OS: macOS 12.4 CPU: (4) x64 Intel(R) Core(TM) i3-8100B CPU @ 3.60GHz Memory: 62.87 MB / 8.00 GB Shell: 5.8.1 - /bin/zsh Binaries: Node: 16.9.1 - ~/.nvm/versions/node/v16.9.1/bin/node npm: 7.21.1 -...
2022-06-22T00:03:37
2022-06-22T00:03:37
{}
NONE
vuejs
core
1,162,516,714
6,157
yyx990803
This is a known issue, because 1. Firefox doesn't support [import maps](https://caniuse.com/import-maps) yet (currently behind a flag in 102+) 2. We use [es-module-shims](https://www.npmjs.com/package/es-module-shims) to shim import map support 3. `es-module-shims` tests native support first which throws the error...
2022-06-22T01:17:49
2022-06-22T01:17:49
{}
MEMBER
vuejs
core
1,165,144,450
6,170
zhazhazhu
> 复制链接已断开... I opened it.
2022-06-24T03:02:18
2022-06-24T03:02:18
{}
NONE
vuejs
core
1,157,269,419
2,513
lidlanca
related issue : https://github.com/vuejs/core/issues/3933
2022-06-16T06:07:28
2022-06-16T06:07:28
{}
CONTRIBUTOR
vuejs
core
1,158,564,050
6,125
LinusBorg
Please follow the issue requirements and provide a reproduction. Also, this is likely an issue with vue-tsc, not vue/core
2022-06-17T07:08:10
2022-06-17T07:08:10
{}
MEMBER
vuejs
core
1,159,167,044
6,130
LinusBorg
This is not a bug and not in need of a fix. The getter will update when a reactive dependency has changed. Since all You do it change a let variable (which is a nonreacrive operation), nothing will updated, and this is expected. You seem to have a misconcsption about the nature and intended use of computed setter...
2022-06-17T19:23:03
2022-06-17T19:23:03
{}
MEMBER
vuejs
core
1,159,610,923
6,086
lidlanca
I actually started a discussion in RFC https://github.com/vuejs/rfcs/discussions/451
2022-06-19T03:53:14
2022-06-19T03:53:14
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
1,161,321,337
6,149
LinusBorg
You need to tell typescript the type of the parameter. That's just how it works. Adn it unrelated to Vue.
2022-06-21T06:33:15
2022-06-21T06:33:15
{}
MEMBER
vuejs
core
1,161,379,193
6,060
LinusBorg
What warnings? What is this about? This feature request doesn't event contain a description or a code example, or a screenshot, or anything allowing us to properly understand your request. Please open a new issue with a proper description of the problem. Feel free to write in chinese if that makes it easier for you.
2022-06-21T07:42:59
2022-06-21T07:42:59
{}
MEMBER
vuejs
core
1,161,700,620
6,154
LinusBorg
Vue prefers setting things as element properties if that property exists on the element: ```js // pseudocode if ('muted' in el) { el.muted = true } else { el.setAttribute('muted', '') } ``` Now, if you set i.e `width` on a video element, the browser will also reflect that as an attribute. But it does n...
2022-06-21T12:45:46
2022-06-21T12:49:11
{ "+1": 4 }
MEMBER
vuejs
core
1,162,210,906
6,156
LinusBorg
that's not how the normal v-for template ref is meant to be used. For your use case, use a function. ```html <div v-for="o in arr" :ref="(e) => o.ref.value = e"> ```
2022-06-21T19:08:59
2022-06-21T19:08:59
{ "+1": 1 }
MEMBER
vuejs
core
1,164,113,864
6,166
liulinboyi
There is an [SFC Example](https://sfc.vuejs.org/#__DEV__eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcbmltcG9ydCBGaWxlVXBsb2FkSGVscGVyIGZyb20gJy4vdGVzdC50cydcblxuY29uc3QgZmlsZSA9IG5ldyBGaWxlVXBsb2FkSGVscGVyKCk7XG5jb25zdCBtc2cgPSByZWYoJ0hlbGxvIFdvcmxkIScpXG48L3NjcmlwdD5cblxuPHRlbXBsYXRlPlxuICA8...
2022-06-23T08:30:36
2022-06-23T08:30:36
{}
MEMBER
vuejs
core
1,156,524,348
6,025
edison1105
close, due to not need this changes.
2022-06-15T14:09:48
2022-06-15T14:09:48
{}
MEMBER
vuejs
core
1,157,403,149
6,118
yyx990803
你的用法每次外层 effect 都在创建新的子 effect，当然越来越多...
2022-06-16T08:50:18
2022-06-16T08:50:18
{}
MEMBER
vuejs
core
1,158,057,040
5,104
tjx666
> `defineProps` must be a top-level call with the exception of `withDefaults`. > > Also with reactivity transform, there is no need to use `toRefs()` on it. @yyx990803 This is my use case: ```vue <script setup lang="ts"> import { ref, onMounted, watch, toRefs } from 'vue'; import * as monaco from 'monac...
2022-06-16T19:30:23
2022-06-16T19:31:03
{}
NONE
vuejs
core
1,158,514,445
3,671
allanrosero
+1
2022-06-17T05:47:21
2022-06-17T05:47:21
{}
NONE
vuejs
core
1,159,244,063
6,130
nros
Thank you very much that you have taken your time to answer. I am really grateful! I thought there might be none. I am sorry to have bothered you. Now I see the way to use it is with underlying 'ref()' storage, which I have missed previously. Therfore, I can see your point that there is not realy a need to change th...
2022-06-17T21:38:13
2022-06-17T21:38:13
{}
NONE
vuejs
core
1,159,556,958
6,031
wsafight
Hello, I went to check the petite-vue source code. - template. Because it is not based on virtual DOM, the instructions of this library are based on DOM APIs such as el.parentElement, template is not a real dom node, so it cannot be used here - v-for and v-if. Its instructions are independent. Both v-if and v-for hav...
2022-06-18T20:33:06
2022-06-18T20:34:13
{ "+1": 3 }
NONE
vuejs
core
1,162,518,534
6,131
yyx990803
~~Custom Elements v1 is only fully supported in Chrome 67+: https://caniuse.com/?search=custom%20elements~~
2022-06-22T01:21:40
2022-06-22T01:24:15
{}
MEMBER
vuejs
core
1,161,623,266
4,294
ckvv
As a workaround, the value can be used instead of the type definition ❌As follows I encapsulated an input component with a label ```vue <script setup lang="ts"> import { ElInput } from "element-plus"; import type { InputEmits, InputProps } from "element-plus"; defineProps< InputProps & { label?: str...
2022-06-21T11:32:07
2022-06-22T04:46:41
{ "-1": 6 }
NONE
vuejs
core
1,156,509,801
6,092
shengxinjing
[oneline demo](https://deploy-preview-6092--vue-sfc-playground.netlify.app/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgaXNTZWxlY3QgPSByZWYodHJ1ZSlcbmZ1bmN0aW9uIHRvZ2dsZSgpe1xuICBpc1NlbGVjdC52YWx1ZSA9ICFpc1NlbGVjdC52YWx1ZVxufVxuPC9zY3JpcHQ+XG5cbjx0ZW1wbGF0ZT5cbiAgPGgxIEBjbGljaz1c...
2022-06-15T13:57:30
2022-06-15T13:57:30
{}
CONTRIBUTOR
vuejs
core
1,158,417,154
5,712
kikyouink
> > > I am version 3.2.33, encountered the same problem as you, and then I got the latest version number, 3.2.37, after the upgrade can be > > > > > > 两个中国人在这说英语，难为你了哈哈哈哈 > > 兄弟，我还有个问题 ![image](https://user-images.githubusercontent.com/72638366/174212141-b912c730-3e25-4b56-91a9-5cbc1a42b116.png) 我生成.d.ts文件的时候全红...
2022-06-17T02:27:52
2022-06-17T02:27:52
{}
NONE
vuejs
core
1,158,665,184
6,118
jackZmym
font{ line-height: 1.6; } ul,ol{ padding-left: 20px; list-style-position: inside; } 好滴，我的想法有点问题，谢谢尤大。 ...
2022-06-17T09:06:12
2022-06-17T09:06:12
{}
NONE
vuejs
core
1,161,579,407
6,151
edison1105
请先确保minimal reproduction能运行。
2022-06-21T10:47:13
2022-06-21T10:47:13
{}
MEMBER
vuejs
core
1,161,826,290
6,152
KaelWD
b60cff052c880b2965d06007f0ec4d0349ab47c0 didn't account for disabled teleport, `nextNode` is the teleport content instead of `<!--teleport end-->`
2022-06-21T14:31:00
2022-06-21T14:31:00
{}
CONTRIBUTOR
vuejs
core
1,163,300,219
6,159
chenxch
[playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2IGZvbnQtc2FucyBwPVwieC00IHktMTBcIiB0ZXh0PVwiY2VudGVyIGdyYXktNzAwIGRhcms6Z3JheS0yMDBcIj5cbiAgICA8Q29tcCB2LW1vZGVsPVwibXZcIiA6b3B0aW9ucz1cIlt7IGxhYmVsOiAnbGFiZWwxJywgdmFsdWU6IHsgaWQ6IDEgfSB9LCB7IGxhYmVsOiAnbGFiZWwyJywgdmFsdWU6IHsgaWQ6IDIgfSB9XVwi...
2022-06-22T15:57:53
2022-06-22T15:57:53
{}
NONE
vuejs
core
1,164,738,249
6,168
liulinboyi
> Here's why this is happening: > > in `<script setup>`: > > * the generated render function can pass the ref itself to the vnode, and > * when the ref's value is set, we read the current value in the process, thereby registering it as a reactive dependency. > > in normal `setup()`: > > * the generated ren...
2022-06-23T18:30:41
2022-06-23T18:30:41
{}
MEMBER
vuejs
core
1,156,507,026
6,092
shengxinjing
> When we switch classes, the patchClass is passed to "", resulting in the class attribute not being removed <img width="1225" alt="image" src="https://user-images.githubusercontent.com/1905176/173844558-767d4fdb-df79-49a2-af12-0dca79b8b498.png">
2022-06-15T13:55:19
2022-06-15T13:55:19
{}
CONTRIBUTOR
vuejs
core
1,158,404,504
5,712
kikyouink
> I am version 3.2.33, encountered the same problem as you, and then I got the latest version number, 3.2.37, after the upgrade can be 两个中国人在这说英语，难为你了哈哈哈哈
2022-06-17T02:19:08
2022-06-17T02:19:08
{}
NONE
vuejs
core
1,159,398,932
6,128
LinusBorg
The goal of Vue 2.7 is *not* do be 100% compatible with Vue 3. The goal of Vue 3 is to backport some of the bigger Vue 3 features so that people who need to stay on Vue 2 can use them. The APIs you mentioned are implementation details unique to Vue 3 and its new vdom, and they will not be backported.
2022-06-18T08:43:08
2022-06-18T08:43:08
{}
MEMBER
vuejs
core
1,162,513,722
6,151
yyx990803
This is non-documented behavior and is not supported. Correct usage is using `<component :is="">` so that the vnode is created during the render: https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcbmltcG9ydCBjcmVhdGUgZnJvbSAnLi9jcmVhdGUudHMnXG5cbmNvbnN0IG1zZyA9IHJlZigna...
2022-06-22T01:11:30
2022-06-22T01:11:30
{}
MEMBER
vuejs
core
1,162,592,538
6,026
iwusong
Comments cannot be ignored directly
2022-06-22T03:22:48
2022-06-22T03:22:48
{}
CONTRIBUTOR