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
942,543,281
4,791
posva
https://github.com/vuejs/rfcs/discussions/369
2021-10-13T17:19:23
2021-10-13T17:19:23
{}
MEMBER
vuejs
core
943,108,590
4,795
posva
I suspect this is expected as mentioned in the other issue but I also see how this would be very useful.
2021-10-14T07:57:56
2021-10-14T07:57:56
{}
MEMBER
vuejs
core
943,274,437
4,797
LinusBorg
if you change `@vue/compiler-sfc` to version "3.2.20" in package.json it works. the codesandbox seems to use an older version. It also works in the [playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2IHJlZj1cInNsaWRlclwiIGNsYXNzPVwia2Vlbi1zbGlkZXJcIj5cbiAgICA8ZGl2IGNsYXNzPVwia2Vlbi1zbGlkZXJfX...
2021-10-14T11:38:28
2021-10-14T11:38:28
{}
MEMBER
vuejs
core
944,481,748
4,792
LinusBorg
Sidenote: I'm not sure yet if this also fixes #4789 as that one doesn't involve a number prop. But I couldn't identify another part of the code that could be responsible yet.
2021-10-15T17:43:23
2021-10-15T17:43:23
{}
MEMBER
vuejs
core
946,295,692
4,783
soulsam480
Any updates on the related PR getting merged ?
2021-10-19T01:39:17
2021-10-19T01:39:17
{}
NONE
vuejs
core
947,514,837
4,823
Dedicatus546
it seems that it can not take effect when use `:slotted()` in `<style module>` `:slotted` in `<style scoped>` will let content of slot add `data-v-xxxx-s` and the corresponding css will add `[data-v-xxxx-s]`. but `<style module>` just generate the unique classname. maybe we can generate a unique slot classnam...
2021-10-20T09:59:26
2021-10-20T09:59:26
{ "laugh": 1 }
NONE
vuejs
core
943,926,798
4,799
lifeilu
> Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js). > > Closing because there is no repro. Hi, thanks ...
2021-10-15T02:11:19
2021-10-15T02:11:19
{}
NONE
vuejs
core
944,297,337
4,799
lifeilu
> OP can open a new issue when they have a runnable reproduction demonstrating the problem. I have created a repo(https://github.com/lifeilu/vue-mf-demo.git), which can demonstrate the problem of child components not rendered. Hope to get your advice.
2021-10-15T13:21:15
2021-10-15T13:23:48
{}
NONE
vuejs
core
944,956,310
4,810
cyfung1031
> Use the chat or the forum for questions, thanks <s>I cannot find the chat or the forum in https://github.com/vuejs/vue-next/ </s> ok.. I found the [forum](http://forum.vuejs.org/) and I think it is a valid feature request if there is no such thing for `<script setup>` please re-open this issue... -------- ...
2021-10-16T17:06:50
2021-10-16T20:10:13
{ "+1": 6 }
NONE
vuejs
core
945,551,905
1,033
filipecruz
@olemarius did you find more info on this?
2021-10-18T08:56:59
2021-10-18T08:56:59
{}
NONE
vuejs
core
945,553,717
3,298
tcstory
wirte transform function for every custom directive is too bad
2021-10-18T08:57:56
2021-10-18T08:57:56
{}
NONE
vuejs
core
945,879,066
1,033
znck
I have a monorepo with one package depending on Vue and other on react. I use pnpm which does not hoists dependencies. Then I have a tsconfig.json for each package. Hence, no JSX conflicts. But If I have to use Vue and react in same package/file, avoiding conflict is not possible.
2021-10-18T15:12:59
2021-10-18T15:13:51
{}
MEMBER
vuejs
core
946,470,102
4,815
LinusBorg
Caused by https://github.com/vuejs/vue-next/commit/f4639e0a36abe16828b202d7297e1486653b1217 Not limited to SSR apps. We should find a way to skip this `setTimeout`, (or potentially the whole devtools setup call?*) when we are: a) in running tests b) in jest c) in jsdom ([detection](https://github.com/jsdom/...
2021-10-19T08:13:47
2021-10-19T12:37:17
{}
MEMBER
vuejs
core
947,131,719
4,766
aparajita
@yyx990803 Thank you!!! You are the man!
2021-10-19T21:48:36
2021-10-19T21:48:36
{}
NONE
vuejs
core
947,492,625
4,823
Dedicatus546
i think you can use `<style scoped>` and `<style module>` together. i test in vue^3.2.20 and it can work well.
2021-10-20T09:32:13
2021-10-20T09:32:13
{}
NONE
vuejs
core
943,362,038
4,797
LinusBorg
And it worked in your codesandbox when I sued the appropriate compiler version in dependencies, that's why I closed it. You **had** it in dependencies, but with version `"3.0.0-0"`. I don't know what's up with the current state of the sandbox though.
2021-10-14T13:32:25
2021-10-14T13:34:06
{}
MEMBER
vuejs
core
943,372,173
4,662
pawel-marciniak
> We will solve this, it might take a few more days or weeks though. @LinusBorg Ok, thanks for quick reply, it's good to know that it will be solved at some point in the future :)
2021-10-14T13:43:54
2021-10-14T13:43:54
{}
NONE
vuejs
core
944,098,774
4,799
LinusBorg
OP can open a new issue when they have a runnable reproduction demonstrating the problem.
2021-10-15T08:20:34
2021-10-15T08:20:34
{}
MEMBER
vuejs
core
944,468,609
4,805
LinusBorg
I just ran the Vue 3 example wih `npm start` and this is what I see: <img width="1161" alt="Bildschirmfoto 2021-10-15 um 19 18 40" src="https://user-images.githubusercontent.com/1444526/137527579-8e86aaed-e583-4d10-aa68-c1a137e03f44.png"> Looks like everything is working? For the record though, like with react...
2021-10-15T17:21:17
2021-10-15T17:21:17
{}
MEMBER
vuejs
core
944,957,719
4,812
kolaente
Sure. Since I got an error "This is likely a vue internals bug, please open an issue" I figured I might as well do that. A better error message, indicating that keys must always be unique, even if only one element with the same key ever exists at the same time would've been helpful. I guess that's a feature request ...
2021-10-16T17:12:44
2021-10-16T17:12:44
{}
NONE
vuejs
core
946,278,829
4,679
edison1105
Maybe should avoid catch `BlockTree` if `patchFlag` is bail. ![image](https://user-images.githubusercontent.com/3705199/137826435-78ce6b06-5a78-4f15-bf39-003448b4ac04.png)
2021-10-19T00:58:46
2021-10-19T12:57:49
{}
MEMBER
vuejs
core
947,499,700
838
klwfwdk
@Eyran 在vscode中装上volar插件 其实能够实现子组件的方法和属性的类型推导
2021-10-20T09:41:13
2021-10-20T09:41:13
{}
CONTRIBUTOR
vuejs
core
944,559,468
4,789
flanagankp
thanks for the update
2021-10-15T19:02:47
2021-10-15T19:02:47
{}
NONE
vuejs
core
944,543,408
4,803
benkroeger
updated [SFC](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCBDb21wIGZyb20gJy4vQ29tcC5qcydcbjwvc2NyaXB0PlxuXG48dGVtcGxhdGU+XG4gIDxDb21wIC8+XG48L3RlbXBsYXRlPiIsImltcG9ydC1tYXAuanNvbiI6IntcbiAgXCJpbXBvcnRzXCI6IHtcbiAgICBcInZ1ZVwiOiBcImh0dHBzOi8vc2ZjLnZ1ZWpzLm9yZy92dWUucnVudGltZS5lc20tYnJvd3Nlci5qc1w...
2021-10-15T18:55:14
2021-10-15T19:03:07
{ "+1": 1 }
NONE
vuejs
core
944,879,374
4,808
ygj6
Seems like duplicate of #4783, may have been solved by https://github.com/vuejs/vue-next/pull/4790
2021-10-16T08:19:48
2021-10-16T08:19:48
{}
MEMBER
vuejs
core
944,945,146
4,813
posva
Provide gives a variable to the children, not the current instance and this is by design as otherwise it would overwrite existing properties.
2021-10-16T16:18:30
2021-10-16T16:18:30
{}
MEMBER
vuejs
core
946,434,075
4,358
zhenzhenChange
是的,这个问题依然会出现,只不过出现的频率可能就是偶尔一两次,解决的办法就是调整他们的位置、换行、加空行 ```json { "dependencies": { "vue": "^3.2.20" }, "devDependencies": { "@vue/compiler-sfc": "^3.2.20", "vite": "^2.6.7" } } ```
2021-10-19T07:20:43
2021-10-19T07:20:43
{}
NONE
vuejs
core
946,638,452
4,788
posva
Not sure if this would be enough for cases like `base-transition` and such
2021-10-19T11:41:24
2021-10-19T11:41:24
{}
MEMBER
vuejs
core
947,425,752
4,821
posva
As you can imagine, you are not supposed to manually declare a property named `__v_isReactive` in an object you give to `reactive()`
2021-10-20T08:04:17
2021-10-20T08:04:17
{}
MEMBER
vuejs
core
947,507,407
4,823
sadeghbarati
yeah I know, in a component both `scoped` and `module` work but when using the _slot_, for styling slotted content with `:slotted()` only `scoped` works
2021-10-20T09:49:10
2021-10-20T09:49:10
{}
NONE
vuejs
core
942,322,674
4,789
LinusBorg
duplicate of #4716
2021-10-13T13:43:45
2021-10-13T13:43:45
{}
MEMBER
vuejs
core
943,033,905
4,793
LinusBorg
I can't reproduce this with a fresh Vite project, and you didn't provide an actual reproduction of the issue. Closing.
2021-10-14T06:40:15
2021-10-14T06:40:15
{}
MEMBER
vuejs
core
944,092,456
4,799
edison1105
ping @posva @LinusBorg
2021-10-15T08:11:06
2021-10-15T08:11:48
{}
MEMBER
vuejs
core
944,130,599
4,800
joleal
I've created a repo where the issue can be reproduced. Let me know if you need any additional information. Thanks!
2021-10-15T09:08:20
2021-10-15T09:08:20
{}
NONE
vuejs
core
947,418,399
4,387
ycingit
> I have fixed @danyadev's project: https://github.com/ygj6/vue3-bug/tree/bug-2 > > Hope it could help you. ![image](https://user-images.githubusercontent.com/23759037/138051159-a9400d73-07a3-4ee8-901a-e2393d28cb46.png) Version 3.2.20 Steps to reproduce 当a组件被keep-alive缓存,切换到b组件,再切换回a组件,对a组件 setup 进行代码更新,h...
2021-10-20T07:54:17
2021-10-20T08:35:20
{}
NONE
vuejs
core
947,652,201
4,826
posva
Add an error component: https://v3.vuejs.org/guide/migration/async-components.html#_3-x-syntax Please, next time consider using the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js) for questions first. But feel free to come back...
2021-10-20T13:11:33
2021-10-20T13:11:33
{}
MEMBER
vuejs
core
943,356,237
4,797
riderx
@LinusBorg i finally found the issue if i upgrade to "@vitejs/plugin-vue": "^1.9.3" and "vite": "^2.6.7" it works
2021-10-14T13:25:52
2021-10-14T13:25:52
{}
NONE
vuejs
core
944,085,820
4,799
lifeilu
> > The child components not rendered. Is it a bug? Hope to get your advice. > > I think this is not a vue-core bug. maybe relate to module-federation. I have tried vue2 component use module-federation, it works well. And i have tried to change the child components using defineAsyncComponent, and found that the...
2021-10-15T08:04:58
2021-10-15T08:04:58
{}
NONE
vuejs
core
944,944,549
4,812
posva
The repro is way too big for us to check it but keys must be unique anyway. Remember to use the chat of forums for questions!
2021-10-16T16:16:00
2021-10-16T16:16:00
{}
MEMBER
vuejs
core
698,097,914
2,220
HcySunYang
You should use the `defineComponent`: https://v3.vuejs.org/api/global-api.html#definecomponent
2020-09-24T04:03:03
2020-09-24T04:03:03
{ "+1": 2 }
MEMBER
vuejs
core
699,118,027
2,239
posva
In that scenario, you should use `transition-group` in both Vue 2 and Vue 3, and put the `v-for` on the inner `div`
2020-09-25T19:39:32
2020-09-25T19:39:32
{}
MEMBER
vuejs
core
699,835,892
2,231
eddeisling
The same behaviour with `watchEffect` ```js const { computed, watchEffect, ref } = Vue; const source = ref(0); const isZero = computed(() => source.value === 0); watchEffect(() => console.log(isZero.value)); // fires every second setInterval(() => source.value++, 1000); ```
2020-09-28T07:36:43
2020-09-28T07:37:26
{}
NONE
vuejs
core
699,959,345
2,255
leopiccionia
I think it's expected and correct behavior. The `marquee` tag is obsolete, and shouldn't be used in new code. Notice that the behavior is also consistent with other obsolete HTML and SVG tags.
2020-09-28T11:52:42
2020-09-28T11:53:21
{}
CONTRIBUTOR
vuejs
core
700,068,852
2,242
andrew0
I've found some references [here](https://github.com/benjamn/recast#source-maps) and [here](https://github.com/Rich-Harris/magic-string#sgeneratemap-options-) to "high resolution" source maps that map each individual character to ensure completely accurate column numbers for errors, so it seems like that is what this c...
2020-09-28T15:09:46
2020-09-28T15:09:46
{}
NONE
vuejs
core
699,887,270
2,251
posva
This issue seems to be caused by one of the CSS libs, so please open an issue there. You are also sharing your whole project as a reproduction which makes it really hard for us to check
2020-09-28T09:17:56
2020-09-28T15:55:42
{}
MEMBER
vuejs
core
698,199,147
2,221
HcySunYang
@posva yes I do it later
2020-09-24T08:30:00
2020-09-24T08:30:00
{}
MEMBER
vuejs
core
698,707,734
2,015
bjarkihall
@LinusBorg , [this discussion might help](https://github.com/facebook/react/issues/3965), where the terminology "reparenting" is used: Generally the discussion (incl. linked gists+rfc) revolves around the use of keys/instances to map components to their destinations but two libraries also stick out there lately: 1....
2020-09-25T04:04:21
2020-09-25T04:04:21
{ "+1": 2 }
CONTRIBUTOR
vuejs
core
698,900,748
2,228
edison1105
this pr is same as [#2174](https://pan.baidu.com/s/19C0E-XFoZJBRAydC9YIzAw)
2020-09-25T12:29:54
2020-09-25T12:30:54
{ "+1": 1 }
MEMBER
vuejs
core
698,996,073
2,235
unbyte
`this.MASTER_DATA` is a proxy, please use `toRaw` for example, ```js return MASTER_DATA === toRaw(this.MASTER_DATA) ```
2020-09-25T15:30:19
2020-09-25T15:30:19
{}
CONTRIBUTOR
vuejs
core
699,029,686
2,237
eliot-ye
> This is a mistake in the doc. > It should be written in this way > > ```js > h("button", { onClickOnce: () => b.value++ }, `object: ${b.value}`) > ``` If I want to add `passive` dynamically according to the value of props, can I achieve it? How can I do it?
2020-09-25T16:35:04
2020-09-25T16:35:04
{}
NONE
vuejs
core
699,483,062
2,243
posva
Please open the bug in vue-class-component repository
2020-09-26T11:29:04
2020-09-26T11:29:04
{}
MEMBER
vuejs
core
699,539,742
2,246
leopiccionia
The [new behavior](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0023-scoped-styles-changes.md) is that, by default, scoped styles are not applied to the slots. You have to opt-in it via `::v-slotted`.
2020-09-26T19:44:14
2020-09-26T19:45:06
{}
CONTRIBUTOR
vuejs
core
699,874,951
2,246
Shouhua
This is because lost scope id information when create VNode using render function, so runtime will set slotted attribute `data-v-13515282-s`, but button class has been compiled like follows: ` .button[data-v-13515282] { background: crimson; } `. Like @leopiccionia said, adding ::v-slotted(.button) or using te...
2020-09-28T08:55:00
2020-09-28T08:55:00
{}
NONE
vuejs
core
700,430,317
2,260
leopsidom
Okay, but shouldn't `name` be tracked regardless of the `if` statement? The following obviously also works. It stops working after we add an `if` statement: ``` const message = Vue.computed(() => { return `Hello ${name.value}`; }); ```
2020-09-29T05:11:29
2020-09-29T05:17:05
{}
NONE
vuejs
core
700,446,408
777
antoniandre
Is this resolved? In Vue 3.0.0 on a fresh Vue project install, the following still throws an error and doesn't mount component: ```js // import HelloWorld from './components/HelloWorld.vue' export default { name: 'App', components: { HelloWorld: () => import('./components/HelloWorld.vue') } } ``...
2020-09-29T05:42:27
2020-09-29T05:42:27
{}
NONE
vuejs
core
698,105,075
2,214
meteorlxy
Tried to make a minimal repro link: https://codepen.io/meteorlxy/pen/QWNYKwe If the slots of `<Suspense>` have **ANY** child-elements (including comments), the bug occurred. That happens in both `#default` and `#fallback` slots.
2020-09-24T04:30:48
2020-09-24T04:41:56
{}
MEMBER
vuejs
core
698,214,451
2,222
posva
Can you open this in vite repository please? https://github.com/vitejs/vite
2020-09-24T08:59:15
2020-09-24T08:59:29
{}
MEMBER
vuejs
core
698,772,966
2,230
HcySunYang
Vnode can be reused in v3, also in Vue2.5.18+. @posva I think we need to update the documentation.
2020-09-25T07:32:24
2020-09-25T07:32:24
{}
MEMBER
vuejs
core
698,792,466
2,221
FrankFang
Just ask, why not keep html comments in `<pre>` ?
2020-09-25T08:16:09
2020-09-25T08:16:09
{}
NONE
vuejs
core
698,891,108
2,234
tidus2102
Vue 3 doc [https://v3.vuejs.org/guide/list.html#v-for-with-v-if](https://v3.vuejs.org/guide/list.html#v-for-with-v-if) said: "v-for has a higher priority than v-if" and the demo code is use v-if for item: ```html <li v-for="todo in todos" v-if="!todo.isComplete"> {{ todo }} </li>```
2020-09-25T12:05:14
2020-09-25T12:10:09
{}
NONE
vuejs
core
699,022,986
2,237
unbyte
This is a mistake in the doc. It should be written in this way ```js h("button", { onClickOnce: () => b.value++ }, `object: ${b.value}`) ```
2020-09-25T16:21:19
2020-09-25T16:21:19
{}
CONTRIBUTOR
vuejs
core
699,033,722
2,238
LinusBorg
This seems to be a documentation issue. The reason that the dynamic transition component is not working is that the compiler doesn't recognize that you wanted and thank youse a transition component. Combined with the fact that the transition component is now tree-shakable in Vue 3, that means that it has to b...
2020-09-25T16:43:44
2020-09-25T16:43:44
{ "+1": 2, "heart": 1 }
MEMBER
vuejs
core
699,921,581
2,170
ajimix
I'm having the same problem also when migrating from v2 to v3 `this.$el` ends up being null while in v2 it works properly
2020-09-28T10:26:14
2020-09-28T10:26:14
{}
NONE
vuejs
core
700,237,516
2,059
CyberAP
I have suggested a change that might be able to fix that: https://github.com/vuejs/rfcs/pull/215
2020-09-28T19:33:20
2020-09-28T19:33:20
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
698,150,418
1,927
posva
@Fiv5 can you opeen a PR or an issue at vuejs/docs-next repository to track it?
2020-09-24T06:47:35
2020-09-24T06:47:35
{}
MEMBER
vuejs
core
698,834,364
2,231
eddeisling
Oh, i get it. Thank you, it may be closed then
2020-09-25T09:44:52
2020-09-25T09:44:52
{}
NONE
vuejs
core
698,848,924
2,232
HcySunYang
Make `userList` reactive: ```js userList: reactive([ { id: 1, name: "name1", isAudit: false }, { id: 2, name: "name2", isAudit: true }, { id: 3, name: "name3", isAudit: true }, ]) ```
2020-09-25T10:16:46
2020-09-25T10:16:46
{ "+1": 1 }
MEMBER
vuejs
core
699,870,833
2,251
edison1105
I found something. The generated CSS is correct when I remove `animation-iteration-count: 1, 1;`(line 55) and `!important`.
2020-09-28T08:47:00
2020-09-28T08:54:08
{}
MEMBER
vuejs
core
700,148,987
2,219
yyx990803
Thanks!
2020-09-28T16:39:21
2020-09-28T16:39:21
{}
MEMBER
vuejs
core
700,288,280
2,225
posva
Thanks for the boiled down repro!
2020-09-28T21:22:02
2020-09-28T21:22:02
{}
MEMBER
vuejs
core
698,114,907
1,927
Fiv5
> This is expected behavior in v3 Strings passed to `h` are always considered native elements. To use components you need to either explicitly import them or, if they are registered globally, resolve them with `resolveComponent` (see https://github.com/vuejs/rfcs/blob/master/active-rfcs/0008-render-function-api-change....
2020-09-24T05:07:07
2020-09-24T05:07:07
{}
NONE
vuejs
core
698,201,246
2,214
gokhantaskan
> Tried to make a minimal repro link: > > https://codepen.io/meteorlxy/pen/QWNYKwe > > If the slots of `<Suspense>` have **ANY** child-elements (including comments), the bug occurred. > > That happens in both `#default` and `#fallback` slots. The code below is not responding: ```js <template #default> ...
2020-09-24T08:34:11
2020-09-24T08:34:11
{}
NONE
vuejs
core
698,431,153
2,210
CyberAP
`app.use(Plugin, Injectables)` where Injectables is an object containing all your dependencies.
2020-09-24T15:50:39
2020-09-24T15:50:39
{ "+1": 2 }
CONTRIBUTOR
vuejs
core
699,914,428
2,255
edison1105
fix by #2256
2020-09-28T10:10:49
2020-09-28T10:10:49
{}
MEMBER
vuejs
core
699,924,727
2,253
LinusBorg
you shouldn't be doing either of those things ...
2020-09-28T10:33:11
2020-09-28T10:33:11
{}
MEMBER
vuejs
core
700,127,858
2,251
fotijr
Gotcha. OK I will try reproducing directly with PostCSS. Thanks.
2020-09-28T16:01:16
2020-09-28T16:01:16
{}
NONE
vuejs
core
698,151,295
2,220
posva
You need to use `defineComponent` as suggested, in order to get the correct typing inference
2020-09-24T06:49:37
2020-09-24T06:49:37
{}
MEMBER
vuejs
core
698,772,164
2,230
bastarder
if `p` was a custom component, also be rendered successfully
2020-09-25T07:30:27
2020-09-25T07:30:27
{}
NONE
vuejs
core
698,795,313
2,221
HcySunYang
By default, comments are not kept in production, but you can achieve this by providing the `comments: true` option to the compiler
2020-09-25T08:21:54
2020-09-25T08:21:54
{ "+1": 1 }
MEMBER
vuejs
core
699,033,832
2,238
sarangnx
It is working now. [jsfiddle](https://jsfiddle.net/sarangnx/t9L4fznc/24/) All i had to do was add `Transition` and `TransitionGroup` components from `'vue'` package in my `fade-in` component. ``` components: { Transition: Vue.Transition, TransitionGroup: Vue.TransitionGroup, }, ```
2020-09-25T16:43:57
2020-09-25T16:43:57
{}
NONE
vuejs
core
699,540,873
2,246
jmurth1234
I'm not targeting a child component, I'm targeting the element with class button that's inside the `Button` component
2020-09-26T19:55:51
2020-09-26T19:55:51
{}
NONE
vuejs
core
699,576,276
2,184
IndexXuan
@posva please review it, we need it a lot for our code design. Thank you
2020-09-27T02:46:43
2020-09-27T02:46:43
{}
NONE
vuejs
core
698,227,200
2,214
meteorlxy
Made another repro link: https://codesandbox.io/s/vuenext-v300-suspense-reactivity-forked-1v92v?file=/src/index.js - `openBlock() + createBlock()`: BUG - `createVNode()`: OK - `h()`: OK
2020-09-24T09:23:21
2020-09-24T09:23:21
{}
MEMBER
vuejs
core
698,897,367
2,234
jacekkarczmarczyk
https://github.com/vuejs/docs-next/issues/534
2020-09-25T12:21:30
2020-09-25T12:21:30
{}
CONTRIBUTOR
vuejs
core
699,102,861
2,238
posva
@sarangnx can you open the same issue at https://github.com/vuejs/docs-next please?
2020-09-25T19:05:54
2020-09-25T19:05:54
{ "+1": 1 }
MEMBER
vuejs
core
699,516,778
2,226
dev-kuznetsov
I see, thank you
2020-09-26T16:23:43
2020-09-26T16:23:43
{}
NONE
vuejs
core
699,590,453
2,247
RobbinBaauw
Isn't an explicit error better? This is only going to cause more confusion as you may suddenly render more than expected.
2020-09-27T06:00:17
2020-09-27T06:00:17
{ "+1": 3 }
CONTRIBUTOR
vuejs
core
700,123,767
2,251
fotijr
@posva I can create a simpler repo that just shows the issue, but I'll wait to do that until I find the right project that is causing the bug. What do you mean by "cas libs"? I looked through the dependency tree but didn't see anything containing "cas". I'm not familiar with Vue internal architecture, so I'd appreciate...
2020-09-28T15:54:36
2020-09-28T15:56:14
{}
NONE
vuejs
core
700,491,377
2,260
posva
This is expected behavior. You can manually track any dependency by reading it at the top of the computed property like said at https://github.com/vuejs/vue-next/issues/2260#issuecomment-700352862
2020-09-29T06:56:16
2020-09-29T06:56:16
{}
MEMBER
vuejs
core
698,157,528
2,221
posva
Can we add a test that toggles production mode and checks this behavior?
2020-09-24T07:03:57
2020-09-24T07:03:57
{}
MEMBER
vuejs
core
698,243,742
2,223
posva
This is expected to be able to collect dependencies and there it will be documented in docs
2020-09-24T09:56:11
2020-09-24T09:56:11
{}
MEMBER
vuejs
core
698,790,520
2,230
posva
Are you sure? I remember reusing nodes not being possible and one of the reasons to use `cloneVnode`
2020-09-25T08:11:59
2020-09-25T08:11:59
{}
MEMBER
vuejs
core
699,570,182
2,227
waantony
> There is no such syntax, you have to use the function one. Why were you expecting this syntax to work? I found it in official Chinese doc. `https://v3.cn.vuejs.org/guide/render-function.html#v-on`. ![image](https://user-images.githubusercontent.com/42765545/94353426-a00fee80-00a3-11eb-928d-fad29a86f6f9.png) ...
2020-09-27T01:32:20
2020-09-27T01:32:20
{}
NONE
vuejs
core
699,540,677
2,246
leopiccionia
Sorry, I mixed it. `::v-deep` can do the trick, then? Notice in the RFC I previously linked that `::v-deep` syntax was changed since Vue 2.x.
2020-09-26T19:54:11
2020-09-27T02:52:24
{}
CONTRIBUTOR
vuejs
core
699,913,787
2,215
underfin
> New nested async child rendered inside an already resolved suspense no longer puts the suspense into pending state (TODO: components with async setup() should be allowed to declare its own loading state / timeout etc. just like defineAsyncComponent) TODO inside https://github.com/vuejs/vue-next/pull/2099
2020-09-28T10:09:30
2020-09-28T10:09:30
{ "+1": 2 }
MEMBER
vuejs
core
699,918,275
2,215
HcySunYang
Great, nice to know, thanks
2020-09-28T10:18:52
2020-09-28T10:18:52
{}
MEMBER
vuejs
core
700,352,862
2,260
leopsidom
But we are not necessarily want to track access to `firstTime`, only `name` in this case. So ideally it should be only reactive with respect to changes of `name` variable regardless of the value of `firstTime`. A very hack way to make this work is this: ``` const message = Vue.computed(() => { name.value; if ...
2020-09-29T00:27:36
2020-09-29T01:45:20
{}
NONE
vuejs
core
700,384,553
2,260
edison1105
> But we are not necessarily want to track access to `firstTime`, only `name` in this case. So ideally it should be only reactive with respect to changes of `name` variable regardless of the value of `firstTime`. A very hack way to make this work is this: > > ``` > const message = Vue.computed(() => { > name.val...
2020-09-29T02:14:32
2020-09-29T02:22:55
{}
MEMBER
vuejs
core
699,572,272
2,237
waantony
> string concatenation? 😂 What a freak syntax! I still like the object syntax in vue@2.x. 😂
2020-09-27T01:53:49
2020-09-27T01:53:49
{}
NONE
vuejs
core
698,996,968
2,235
laineus
@unbyte Thank you. I understand. :bow: Sorry for taking your time.
2020-09-25T15:31:57
2020-09-25T15:31:57
{}
CONTRIBUTOR