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
542,298,553
297
yyx990803
I'm not sure if these tests are really necessary. These functionalities will be tested as part of higher-level integration tests in `vue`.
2019-10-15T16:31:20
2019-10-15T16:31:20
{}
MEMBER
vuejs
core
542,375,977
300
ZhangJian-3ti
They are mostly very stable items. I think it's a trade off for smaller package size. If you really want to write items separately, just use String template also can achieve the same purpose.
2019-10-15T19:49:36
2019-10-15T19:49:36
{}
CONTRIBUTOR
vuejs
core
542,398,329
281
vue-bot
Hey @alk831, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-15T20:49:16
2019-10-15T20:49:16
{}
CONTRIBUTOR
vuejs
core
542,420,781
306
vue-bot
Hey @dependabot-preview[bot], thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-15T21:52:25
2019-10-15T21:52:25
{}
CONTRIBUTOR
vuejs
core
542,427,995
302
yyx990803
Thanks but I honestly don't think the value provided by these type changes justify the additional complexity they introduce.
2019-10-15T22:15:31
2019-10-15T22:15:31
{}
MEMBER
vuejs
core
542,725,063
313
vue-bot
Hey @pikax, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-16T14:20:05
2019-10-16T14:20:05
{}
CONTRIBUTOR
vuejs
core
542,730,979
318
pikax
Is it worth to add tests for those cases? Since all tests were passing
2019-10-16T14:32:05
2019-10-16T14:32:05
{}
MEMBER
vuejs
core
543,805,412
324
yyx990803
@pikax yes, we will eventually do that. Just leaving it for later to avoid distractions now.
2019-10-18T15:47:48
2019-10-18T15:47:48
{ "+1": 2 }
MEMBER
vuejs
core
541,832,963
281
adamlewkowicz
Prettier has been failing for this commit, so please make sure everything is ok :)
2019-10-14T18:10:33
2019-10-14T18:10:33
{}
CONTRIBUTOR
vuejs
core
541,868,623
281
yyx990803
This is great. Can you add a test case for this?
2019-10-14T19:18:35
2019-10-14T19:18:35
{}
MEMBER
vuejs
core
542,186,214
292
pikax
I see what you mean, this should be enough ```ts type KeyedEvent = KeyboardEvent | MouseEvent | TouchEvent; // ... !(e as KeyedEvent).ctrlKey, ```
2019-10-15T12:26:52
2019-10-15T12:26:52
{}
MEMBER
vuejs
core
542,204,659
294
pikax
some findings: - `indexOf` is faster than set for array of object if the length is less than 40, but performs worse if the list contains string or numbers - lodash.uniq performs much faster in small arrays and faster on arrays > 800 items
2019-10-15T13:13:10
2019-10-15T13:13:10
{}
MEMBER
vuejs
core
543,319,337
315
vue-bot
Thanks again! 💚
2019-10-17T19:09:54
2019-10-17T19:09:54
{}
CONTRIBUTOR
vuejs
core
543,621,600
324
pikax
Personally I don't like filters, they are only a method in disguised. Hiding it under a flag, seems a good approach. @yyx990803 shouldn't we discuss the drop of filters on RFC?
2019-10-18T09:15:22
2019-10-18T09:15:22
{ "+1": 4 }
MEMBER
vuejs
core
543,753,632
331
jo0ger
I think the problem is the inference of `Array<infer V>` ``` ts type ArrayA = Ref<[number, Ref<string>, Ref<Ref<boolean>>, Ref<string>]> ``` The inferred type is `string | number | boolean | Ref<string> | Ref<Ref<boolean>>`,It doesn't extend any type But I think the following is better: ```ts // changed...
2019-10-18T13:42:33
2019-10-18T13:43:46
{}
CONTRIBUTOR
vuejs
core
542,298,561
292
vue-bot
Hey @pikax, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-15T16:31:22
2019-10-15T16:31:22
{}
CONTRIBUTOR
vuejs
core
542,403,650
290
vue-bot
Hey @HcySunYang, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-15T21:03:03
2019-10-15T21:03:03
{}
CONTRIBUTOR
vuejs
core
542,409,295
303
vue-bot
Hey @ivansieder, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-15T21:18:37
2019-10-15T21:18:37
{}
CONTRIBUTOR
vuejs
core
542,420,742
305
vue-bot
Hey @dependabot-preview[bot], thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-15T21:52:17
2019-10-15T21:52:17
{}
CONTRIBUTOR
vuejs
core
542,723,231
312
vue-bot
Hey @soouup, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-16T14:16:15
2019-10-16T14:16:15
{}
CONTRIBUTOR
vuejs
core
542,859,608
319
vue-bot
Hey @pikax, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-16T19:39:53
2019-10-16T19:39:53
{}
CONTRIBUTOR
vuejs
core
542,904,603
321
vue-bot
Hey @dependabot-preview[bot], thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-16T21:44:47
2019-10-16T21:44:47
{}
CONTRIBUTOR
vuejs
core
541,822,525
252
dsseng
@yyx990803 I fixed all the requested changes
2019-10-14T17:50:44
2019-10-14T17:50:44
{}
CONTRIBUTOR
vuejs
core
542,267,835
286
vue-bot
Hey @yeyan1996, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-15T15:23:28
2019-10-15T15:23:28
{}
CONTRIBUTOR
vuejs
core
542,292,220
282
vue-bot
Hey @ayush987goyal, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-15T16:16:09
2019-10-15T16:16:09
{}
CONTRIBUTOR
vuejs
core
542,533,678
301
vue-bot
Hey @Tidyzq, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-16T06:03:12
2019-10-16T06:03:12
{}
CONTRIBUTOR
vuejs
core
542,728,375
318
yyx990803
All of these cases are intentional. We want the flag to **only** be that specific flag.
2019-10-16T14:26:52
2019-10-16T14:26:52
{ "+1": 1 }
MEMBER
vuejs
core
543,317,244
322
yyx990803
This actually doesn't matter because... in production they are all converted into `void 0` by minifiers.
2019-10-17T19:04:09
2019-10-17T19:04:09
{}
MEMBER
vuejs
core
543,318,236
323
vue-bot
Hey @pikax, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-17T19:06:54
2019-10-17T19:06:54
{}
CONTRIBUTOR
vuejs
core
543,636,768
330
laquasicinque
Surely Object would provide the biggest performance increase? https://jsperf.com/regandset/3 Edit: different perf test so that it always returns a boolean
2019-10-18T09:43:33
2019-10-18T09:46:55
{}
CONTRIBUTOR
vuejs
core
542,420,665
304
vue-bot
Hey @dependabot-preview[bot], thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-15T21:52:04
2019-10-15T21:52:04
{}
CONTRIBUTOR
vuejs
core
542,425,133
300
yyx990803
I don't think this makes that much of a difference - I personally find the csv reading just fine.
2019-10-15T22:05:45
2019-10-15T22:05:52
{}
MEMBER
vuejs
core
542,748,173
319
CyberAP
> I'm concern on how our benchmarks are yielding different results 🤔 You last test assigns to `window.i`
2019-10-16T15:07:55
2019-10-16T15:07:55
{}
CONTRIBUTOR
vuejs
core
542,754,916
319
CyberAP
By the way right now `fill` is hilariously slow in Firefox. Maybe it'd be better to extract that into a shared function? Although I don't know if there are any more places where a fixed array is filled. ![image](https://user-images.githubusercontent.com/1462706/66933274-8667c980-f041-11e9-9bd8-740eab85b3c2.png)
2019-10-16T15:21:51
2019-10-16T15:21:51
{}
CONTRIBUTOR
vuejs
core
543,321,488
324
yyx990803
This is very well done... but we are actually considering removing filters in v3. We do need this for v2 compat, so we need to wrap filter-related parts under a [feature flag](https://github.com/vuejs/vue-next/blob/master/rollup.config.js#L161-L162) and reduce its footprint as much as we can when it's not enabled in a ...
2019-10-17T19:16:05
2019-10-17T19:16:05
{ "+1": 3 }
MEMBER
vuejs
core
541,877,428
217
yyx990803
Looks good - yes let's work on `isCustomElement` in a separate PR.
2019-10-14T19:36:17
2019-10-14T19:36:17
{}
MEMBER
vuejs
core
542,740,235
314
vue-bot
Hey @pikax, thank you for your time and effort spent on this PR, contributions like yours help make Vue better for everyone. Cheers! 💚
2019-10-16T14:51:43
2019-10-16T14:51:43
{}
CONTRIBUTOR
vuejs
core
542,774,765
319
pikax
Nice catch, I copied the code from the source code, probably better as you said @yyx990803
2019-10-16T16:04:58
2019-10-16T16:04:58
{}
MEMBER
vuejs
core
543,317,541
315
yyx990803
Thanks!
2019-10-17T19:04:58
2019-10-17T19:04:58
{}
MEMBER
vuejs
core
636,964,895
1,283
leopiccionia
The minified version may have these replacements automatically. But authoring code with more verbose code may be more comfortable.
2020-06-01T16:19:50
2020-06-01T16:19:50
{}
CONTRIBUTOR
vuejs
core
637,233,304
1,284
allowing
![83473684-bd99c680-a4bc-11ea-991d-8df1b839b388](https://user-images.githubusercontent.com/20262949/83475590-3bf86780-a4c1-11ea-8d85-8e8078167d31.jpeg) ![21717E63-79E7-4075-9863-AB7C7AB073B6](https://user-images.githubusercontent.com/20262949/83473697-c5f20180-a4bc-11ea-899f-51659c9d2e5f.jpeg) ![AF846550-EFA5-42C6-...
2020-06-02T02:35:47
2020-06-02T03:07:36
{}
NONE
vuejs
core
639,327,606
1,294
allowing
#1284 iOS 12 got same
2020-06-05T08:09:29
2020-06-05T08:09:29
{}
NONE
vuejs
core
639,640,062
1,304
shortpoet
small update: I tried using a v-if instead of a dynamic import and am getting the same error. It is slightly different in that the active class is still applied when using v-if, whereas dynamic import changes the component (text of button changes) but not the class. I am including a link to this latest commit j...
2020-06-05T17:11:40
2020-06-05T17:11:40
{}
NONE
vuejs
core
637,225,216
1,281
underfin
This is an optimize for many hosited nodes.You can use `static` vnode as same as normal vnode.
2020-06-02T02:10:21
2020-06-02T02:10:21
{}
MEMBER
vuejs
core
640,236,570
1,304
shortpoet
Update: I tried repeating that other thing that (I thought) was causing a bug. It works fine now so clearly that was my code I guess. I just wish I had that link to the specific commit saved/could find that other bug report. In any case, the bug mentioned in this issue still happens even in the latest version of my c...
2020-06-07T15:34:00
2020-06-07T15:34:00
{}
NONE
vuejs
core
641,152,871
1,304
pikax
> I tried making a codesanbox but I'm not sure how to get the new version of vue running there You can use this template https://codesandbox.io/s/vue-alpha-vue-composable-template-mgs1g?file=/src/App.vue
2020-06-09T09:21:20
2020-06-09T09:21:20
{ "+1": 2 }
MEMBER
vuejs
core
641,209,044
1,328
aneryu
#1325
2020-06-09T10:50:22
2020-06-09T10:50:22
{}
CONTRIBUTOR
vuejs
core
641,323,947
1,102
zhengxs2018
@milewski 你有毒,打拼音,弄的我一愣一愣的,使用 ts-ignore 可以先解决
2020-06-09T14:11:43
2020-06-09T14:11:43
{}
NONE
vuejs
core
641,570,736
1,268
yyx990803
Thanks, skipping stringification at the compiler level is safer and more efficient. It also avoids adding more runtime code.
2020-06-09T21:03:24
2020-06-09T21:03:24
{ "+1": 1 }
MEMBER
vuejs
core
642,185,240
1,286
yyx990803
I took another look at this and I think it is better to just bail stringification for all slot content. Pro: ensures child components can always expect to work with vdom nodes regardless of depth. Cons: cannot take advantage of stringification inside slots - which seems to be an ok trade-off since the nodes are s...
2020-06-10T18:32:19
2020-06-10T18:32:19
{}
MEMBER
vuejs
core
637,033,256
1,283
34r7h
fair enough, thanks for the consideration guys
2020-06-01T18:35:06
2020-06-01T18:35:06
{}
NONE
vuejs
core
637,438,491
1,267
cbdiesse
@posva Considering your answer, Can we say, Plugin install mechanism have been changed 1. from Vue instance target, to App root component target ? 2. We can not actually use vue 2 plugin tools/libs in vue 3 ? 3. So constraint to wait for those tools/libs are migrated to vue 3 ? Please advise ... e.g...
2020-06-02T10:10:49
2020-06-02T10:10:49
{}
NONE
vuejs
core
637,721,233
1,285
yyx990803
Yeah we should formalize that - up to this point we've been pretty liberal on the use of ES2015+ features, so there might be a few cases that should be corrected.
2020-06-02T18:18:52
2020-06-02T18:18:52
{}
MEMBER
vuejs
core
638,141,369
1,284
allowing
The reason is iOS 11.3 still not support the Proxy. 🥶🥶🥶I can't believe the Android 6 supported nice so much.
2020-06-03T11:39:16
2020-06-03T11:39:16
{}
NONE
vuejs
core
638,302,277
1,290
pikax
This should be closed based on https://github.com/vuejs/vue-next/issues/1287#issuecomment-638252620
2020-06-03T16:16:51
2020-06-03T16:16:51
{}
MEMBER
vuejs
core
639,319,460
1,284
allowing
It should not be the reason for not supporting ES6. Because iOS 12.4 already supports es6 syntax.
2020-06-05T07:51:58
2020-06-05T07:51:58
{}
NONE
vuejs
core
639,986,144
1,307
KaelWD
https://vue-composition-api-rfc.netlify.app/api.html#torefs
2020-06-06T05:15:36
2020-06-06T05:15:36
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
640,042,147
1,307
posva
I also recommend you to take a look at the main RFC at https://vue-composition-api-rfc.netlify.app/
2020-06-06T11:19:33
2020-06-06T11:19:33
{}
MEMBER
vuejs
core
637,604,350
1,281
pikax
It looks like an unsuspected behaviour because this do hoist per `div`: ```html <div class="section"> <div class="3">Title 1</div> </div> <div class="section"> <div>Title 2</div> </div> <div class="section"> <div>Title 3</div> </div> ``` but this, do hoist to the whole template ```html <div class="se...
2020-06-02T15:08:28
2020-06-02T15:08:28
{}
MEMBER
vuejs
core
638,857,708
1,237
haoqunjiang
Yeah, that makes sense.
2020-06-04T13:45:22
2020-06-04T13:45:22
{ "heart": 1 }
MEMBER
vuejs
core
638,951,509
1,295
yyx990803
https://github.com/vuejs/vue-next/issues/1287#issuecomment-638252620
2020-06-04T16:03:39
2020-06-04T16:03:39
{}
MEMBER
vuejs
core
640,165,000
1,304
underfin
![image](https://user-images.githubusercontent.com/14008915/83961968-245b1d80-a8cb-11ea-89af-8734caae413a.png) I got some error with above image and don‘t get error which is same with you. I cloned your repo just now. Is it miss something for me or you?
2020-06-07T06:30:09
2020-06-07T06:30:09
{}
MEMBER
vuejs
core
640,320,824
1,304
underfin
I pull the lasted code from your repo and do something with you said.You maybe ingore add `task` routes in `routes.json` and I run it success after I add that. Hmm.But I don‘t get the error when click `edit` button.As you say, it work fine with your code.If you still have this bug.Please provider an minimum reporduct...
2020-06-08T01:59:01
2020-06-08T01:59:01
{}
MEMBER
vuejs
core
637,027,083
1,283
yyx990803
Also a tip: in general, it is not recommended to suggest code style changes to other people's codebase. Everyone has their own preferences and you should respect what the authors have chosen to go with unless there are objective performance/correctness concerns.
2020-06-01T18:22:04
2020-06-01T18:22:35
{}
MEMBER
vuejs
core
640,427,070
1,318
pikax
This is a bug, you can replace `:value` with `v-model` until this gets fixed. This bug is caused by the `value` is being assigned before the `select` children are rendered. I'm looking for a fix for it.
2020-06-08T07:42:42
2020-06-08T07:42:42
{ "+1": 2 }
MEMBER
vuejs
core
637,636,064
1,281
yyx990803
There are some internal heuristics based on amount of nodes with bindings to determine whether a piece of content is static hoisted. However I think it's reasonable to bail on multi-element stringification directly inside a slot. i.e. root level nodes inside a slot should be preserved, but they themselves can stringify...
2020-06-02T15:43:27
2020-06-02T15:43:27
{ "+1": 2 }
MEMBER
vuejs
core
640,240,475
1,304
shortpoet
Since that server requires MongoDb and that seems like a lot to ask for this issue, I created a mock server and pushed it in this commit: [mock server](https://github.com/shortpoet/JobDash/tree/0e2236ddbe687c20cfa6715818eff99a70754e5f/dashboard/tests/__mocks__) can be accessed and run by: ``` cd /dashboard/tests/_...
2020-06-07T16:01:42
2020-06-07T16:01:42
{}
NONE
vuejs
core
641,535,348
1,304
shortpoet
@pikax thank you very much for that handy resource! @underfin update: I haven't been able to recreate that bug, even in my own app at this point. My best guess is that it had to do with either the root elements as I mentioned or, and this seems even more likely now, a misuse of provide/inject. As part of th...
2020-06-09T19:53:39
2020-06-09T19:53:39
{}
NONE
vuejs
core
637,688,502
1,237
haoqunjiang
There's the tool called `only-allow`: https://www.npmjs.com/package/only-allow Maybe it's a better alternative?
2020-06-02T17:12:55
2020-06-02T17:12:55
{}
MEMBER
vuejs
core
638,840,484
1,293
cexbrayat
@pikax Sure, done!
2020-06-04T13:16:39
2020-06-04T13:16:39
{}
MEMBER
vuejs
core
639,843,322
1,005
shortpoet
I'm not very experienced so, not sure if it helps, or if this is the correct place, but just in case... I came across this issue when googling the following warning: > Extraneous non-emits event listeners (update-contacts) were passed to component but could not be automatically inherited because component render...
2020-06-05T21:53:47
2020-06-05T21:53:47
{}
NONE
vuejs
core
639,996,159
1,308
underfin
https://github.com/vuejs/vue-next/pull/1269
2020-06-06T06:44:32
2020-06-06T06:44:32
{}
MEMBER
vuejs
core
640,004,565
1,306
underfin
https://github.com/vuejs/vue-next/pull/1230
2020-06-06T07:35:08
2020-06-06T07:35:08
{}
MEMBER
vuejs
core
640,235,239
1,304
shortpoet
That network error is from the API call to the nest server. From the project root run: ``` cd server yarn start ``` That way you only get the reported error. I filed another similar issue which I was looking for just now. I guess it either got deleted or I didn't press the submit button. I thought I ha...
2020-06-07T15:24:08
2020-06-07T15:24:08
{}
NONE
vuejs
core
641,315,225
1,102
milewski
Wo ye you zhege wenti.. you ren zhidao zenme bang?
2020-06-09T13:58:26
2020-06-09T13:58:26
{}
NONE
vuejs
core
641,541,378
1,155
yyx990803
This is actually close to what Optional Props Declaration is, and has the same problem when dealing with attrs fallthrough: - No fallthrough -> use `class` and `style` on the component but find them not applied to root, confusing - Fallthrough -> all the props you intend to use for state only are also applied to ...
2020-06-09T20:06:38
2020-06-09T20:11:01
{ "+1": 1, "confused": 2 }
MEMBER
vuejs
core
641,957,222
1,315
Jackbennett
That makes sense, Just coming back to it though because it works perfectly fine when running in `dev`. You run `build` and find the classes stripped out. No warnings are thrown, should it? I have seen that fragmented root warning message but not doing this. I can see why v-else-if makes much better sense.
2020-06-10T12:01:39
2020-06-10T12:01:39
{}
NONE
vuejs
core
642,253,876
1,306
yyx990803
Closed via https://github.com/fuchunhui/vue-next/commit/a215feda451810251e37dabf5027c9cb0a2b82bf
2020-06-10T20:56:45
2020-06-10T20:56:45
{}
MEMBER
vuejs
core
638,252,620
1,287
yyx990803
This is expected. If you need to remount the same app, put your app creation logic in a factory function and call it again to create a new app instance.
2020-06-03T14:56:36
2020-06-03T14:56:36
{}
MEMBER
vuejs
core
638,612,373
1,237
limichange
@sodatea I think a little code better than include a package.
2020-06-04T05:33:20
2020-06-04T05:33:20
{}
CONTRIBUTOR
vuejs
core
639,475,953
1,294
AlexandreBonaventure
@allowing I don't think it is the same issue at all. --- I fixed the issue here: #1302 Believe or not, I found one of the weirdest issue with destructuring on Edge 44, and this is what is causing the issue. Somehow, it seems like destructuring arrays with object syntax is straight up broken on edge 44. I had a h...
2020-06-05T13:20:48
2020-06-05T13:21:29
{}
CONTRIBUTOR
vuejs
core
641,516,128
1,331
benmccann
Thanks for taking the time to investigate and explain!
2020-06-09T19:13:21
2020-06-09T19:13:21
{}
NONE
vuejs
core
641,584,251
1,230
yyx990803
- `context.parent` is only usable during the normal transform phase. Static hoisting phase is a post-transform so `context.parent` is not accurate in this case. - No need to bail on `p` because anything can be placed inside `p` can be placed in `div`. Also `colspan` is not an element. - It should be enough to jus...
2020-06-09T21:15:53
2020-06-09T21:15:53
{}
MEMBER
vuejs
core
641,591,507
1,254
yyx990803
Closed via https://github.com/vuejs/vue-next/commit/a938b61edca63c1f03f99b85de3f2a3a519268e6
2020-06-09T21:27:49
2020-06-09T21:27:49
{}
MEMBER
vuejs
core
636,965,998
1,283
posva
Thank you but as said in the others PR, we find the version with if/else to be more readable in most scenarios.
2020-06-01T16:20:44
2020-06-01T16:20:44
{}
MEMBER
vuejs
core
637,026,034
1,276
yyx990803
If WeChat browser doesn't support ES2015 then the current version of `vue-next` won't run. That's expected. Otherwise, you'll have to wait for the IE11 compatible build.
2020-06-01T18:19:44
2020-06-01T18:19:44
{}
MEMBER
vuejs
core
638,180,304
1,284
Mister-Hope
> The reason is iOS 11.3 still not support the Proxy. 🥶🥶🥶I can't believe the Android 6 supported nice so much. HHHHH 🤣 Why unbelievable?
2020-06-03T12:59:37
2020-06-03T12:59:37
{}
NONE
vuejs
core
639,207,403
1,290
underfin
Yeah.Do it with https://github.com/vuejs/vue-next/pull/1297.
2020-06-05T01:40:08
2020-06-05T01:40:08
{}
MEMBER
vuejs
core
640,810,252
1,304
shortpoet
Hey so I tried to use the tabs/dynamic import again and the bug reappeared. I tried making a codesanbox but I'm not sure how to get the new version of vue running there. Is there an example sandbox with basic config you can send me? I can then try and reproduce the error using the same thing I am trying. For the re...
2020-06-08T18:55:57
2020-06-08T18:55:57
{}
NONE
vuejs
core
642,004,840
1,335
vue-bot
Hello, thank you for taking time filling this issue! However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic...
2020-06-10T13:22:00
2020-06-10T13:22:00
{}
CONTRIBUTOR
vuejs
core
642,253,588
1,303
yyx990803
This is required for hydration to properly/efficiently pickup the boundaries of fragments.
2020-06-10T20:56:12
2020-06-10T20:56:20
{}
MEMBER
vuejs
core
637,496,356
1,281
underfin
The optimization happend when node count and props count reach the dafalut threshold value.Thi is why first case is diffrent of the second. And The optimization is not support for runtime compiler on now. For the case `let cards = this.$slots.default.map((slot) => h(Card, [slot]))`, you still can do it with v2. For t...
2020-06-02T12:04:02
2020-06-02T12:04:02
{}
MEMBER
vuejs
core
637,580,794
1,281
sneppy
> you still can do it with v2 You mean, I can do it with Vue 2.x? Because, of course If i simply do this in Vue 3: ```javascript let cards = slots.default().map((slot) => h(Card, [slot])) ``` I end up with a single `Card` component which contains the three `div`s, which is not what I want. > maybe you can...
2020-06-02T14:30:48
2020-06-02T14:30:48
{}
NONE
vuejs
core
638,043,660
1,239
dependabot-preview[bot]
Superseded by #1288.
2020-06-03T08:25:23
2020-06-03T08:25:23
{}
CONTRIBUTOR
vuejs
core
639,310,918
1,284
allowing
The situation is not optimistic, today found iOS 12.4 is not compatible
2020-06-05T07:33:34
2020-06-05T07:33:34
{}
NONE
vuejs
core
640,380,279
1,311
tangjinzhou
Sorry. I closed this issue. In fact, the [jsx](https://github.com/vueComponent/jsx) I used should be the problem of the jsx plugin.
2020-06-08T05:36:38
2020-06-08T05:37:24
{}
CONTRIBUTOR
vuejs
core
640,816,745
1,304
shortpoet
I think I have managed to isolate the bug a bit. The error disappeared again. I realized that it happens when I place the parent component that hold a nested dynamic import at the root of a template. When I nest the parent component even in one 'div', it works with no error.
2020-06-08T19:09:08
2020-06-08T19:09:08
{}
NONE
vuejs
core
641,039,559
1,324
zhangzhonghe
Should be like this ```TypeScript export function useMappedRef<T, MT>( original: Ref<T>, fn: (newVal: T) => MT ) { const mapped: Ref<UnwrapRef<MT>> = ref(fn(original.value)); } ```
2020-06-09T05:34:50
2020-06-09T05:34:50
{}
MEMBER
vuejs
core
641,123,895
1,326
vue-bot
Hello, thank you for taking time filling this issue! However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic...
2020-06-09T08:32:04
2020-06-09T08:32:04
{}
CONTRIBUTOR
vuejs
core
641,341,942
1,324
dodas
Thank you both. @zhangzhonghe: using your suggestion, I would still need to cast every time I assign to `mapped.value`. @pikax: that works. However, is that how it's supposed to work? Can it be improved? I migrated from @vue/composition-api 0.4.0 where this used to work without casting or explicit `UnwrapRef`...
2020-06-09T14:40:51
2020-06-09T14:46:26
{}
NONE