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
587,684,553
737
tesla3327
I was playing around with the composition API, building a todo list where you can add items created by other sources (like `useMousePosition`). ```js const { x, y } = useMousePosition(); const list = ref([x, y, 'hello', 'world']); ``` Or in this case, where one item in the list is updated from a `setInterval`:...
2020-02-18T19:13:55
2020-02-18T19:13:55
{}
NONE
vuejs
core
589,658,271
756
yyx990803
I'll merge this since this keeps the behavior consistent with 2.x. We will revisit the change as part of the RFC discussion.
2020-02-21T13:43:50
2020-02-21T13:43:50
{}
MEMBER
vuejs
core
589,706,220
737
yyx990803
/cc @jods4 would be interesting to hear your thoughts on this.
2020-02-21T15:37:54
2020-02-21T15:37:54
{}
MEMBER
vuejs
core
589,916,560
737
yyx990803
Arrays will no longer unwrap refs after 775a7c2
2020-02-22T04:20:28
2020-02-22T04:20:28
{ "+1": 1 }
MEMBER
vuejs
core
590,094,360
767
yyx990803
The patch flags can only be analyzed via static analysis at compile time.
2020-02-23T17:32:38
2020-02-23T17:32:38
{}
MEMBER
vuejs
core
589,743,714
759
clemyan
~~So you are saying `ref` should be typed as `<T>(v: T) => Ref<UnwrapRef<T>>`?~~ Oops, didn't see a commit closed this issue.
2020-02-21T17:04:37
2020-02-24T04:22:00
{}
NONE
vuejs
core
590,900,414
772
jods4
OK, will try. I assume a `watch` started in `onMounted` is cleaned up automatically when the component is unmounted, just like it would be if created in `setup`? Which makes me wonder: what is the precise rule? When can I start a `computed`/`watch`/`watchEffect` and have it disposed automatically? When can I not?
2020-02-25T14:42:51
2020-02-25T14:42:51
{}
CONTRIBUTOR
vuejs
core
591,072,232
772
yyx990803
I think it never worked inside slots - that's a separate issue though. For now you can use a function ref to get around that: ``` html <v-comp> <div :ref="el => (y = el)"></div> </v-comp> ```
2020-02-25T21:13:58
2020-02-25T21:13:58
{}
MEMBER
vuejs
core
591,190,825
772
yyx990803
It's been fixed in 3eab143
2020-02-26T01:38:36
2020-02-26T01:38:36
{ "hooray": 1 }
MEMBER
vuejs
core
591,535,370
784
ysj16
I found the warn just now.. I will try to fix the class patch error in this situation. ````"vue.global.js:4748 [Vue warn]: Extraneous non-props attributes (class) were passed to component but could not be automatically inherited because component renders fragment or text root nodes."````
2020-02-26T17:05:34
2020-02-26T17:08:55
{}
CONTRIBUTOR
vuejs
core
587,382,354
731
jods4
@yyx990803 as you said it's not really a problem because `href` just works. Surprisingly, most if not all articles about using svg icons I found online still use `xlink:`. I was following this pattern and it took me a _long_ while to figure out why it doesn't work. This was really frustrating. So if support is dr...
2020-02-18T10:12:01
2020-02-18T10:12:01
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
591,099,856
768
yyx990803
Your root instance is still using in-DOM template (in `index.html`) which requires runtime compilation.
2020-02-25T22:18:39
2020-02-25T22:18:39
{ "+1": 1, "hooray": 1 }
MEMBER
vuejs
core
592,310,248
784
ysj16
Got it
2020-02-28T04:41:12
2020-02-28T04:41:12
{}
CONTRIBUTOR
vuejs
core
586,372,511
724
jods4
This was `alpha.4`. I tried to create a repro on the template explorer but I noticed it worked... that's why I couldn't put up a repro quickly. I was in a hurry to leave work, I can try `master` this week-end or Monday to confirm if the bug is still there. If you can publish an `alpha.5` it might even be better.
2020-02-14T16:50:57
2020-02-14T16:50:57
{}
CONTRIBUTOR
vuejs
core
589,001,316
745
rigor789
@lmiller1990 I'm just looking through `runtime-dom` and `compiler-dom`, looks like the usage is less than I thought initially. From a quick scan though I would probably use `makeMap`, some of the general utils like `isPromise, isPlainObject...` (from index.ts), maybe the `patchFlags` and `shapeFlags` but I'm not sure i...
2020-02-20T12:40:01
2020-02-20T12:40:01
{}
CONTRIBUTOR
vuejs
core
589,607,252
756
yyx990803
I think it's questionable whether we want to keep this behavior, as it has led to confusing behavior in the past, e.g. a parent scope rule accidentally affecting the child because the child root happens to have the same class name: In parent: ``` vue <template> <Child /> </template> <style scoped> .foo {...
2020-02-21T11:04:15
2020-02-21T11:04:29
{}
MEMBER
vuejs
core
589,618,763
745
rigor789
**Update**: We've settled on a similar monorepo/build setup as vue, and for now we have a copy of the shared package in there. This works well for now! I have some of the basics (creating elements, patching simple props) up and running with NS and Vue 3 - it's looking promising! Thank you @yyx990803 for making t...
2020-02-21T11:40:29
2020-02-21T11:40:29
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
590,458,456
765
jods4
~Why not fix the typings?~ ~If `watchEffect` is a separate api (btw... why?) then `deep` makes no sense, so remove it from `options`?~ ~What also makes no sense to me is returning a value from `watchEffect` callback. It's just discarded right? If you want to cache a result then the api would be `computed`.~ ED...
2020-02-24T17:41:19
2020-02-24T17:45:17
{}
CONTRIBUTOR
vuejs
core
591,379,573
782
vankop
@hareku Thats why I created issue..
2020-02-26T11:29:21
2020-02-26T11:29:21
{}
NONE
vuejs
core
591,979,498
784
ysj16
Done. @yyx990803
2020-02-27T13:47:48
2020-02-27T13:47:48
{}
CONTRIBUTOR
vuejs
core
592,287,250
738
yyx990803
FYI this behavior will be reverted in the next release (back to implicit deep unwrap)
2020-02-28T03:00:19
2020-02-28T03:00:19
{ "+1": 1 }
MEMBER
vuejs
core
590,929,074
776
yyx990803
Oh nvm, I see you are referencing #766
2020-02-25T15:38:03
2020-02-25T15:38:03
{ "laugh": 1 }
MEMBER
vuejs
core
591,075,066
768
yyx990803
See https://github.com/vuejs/vue-next/tree/master/packages/vue#which-dist-file-to-use The default build used with a bundler is the runtime-only build so it doesn't support on-the-fly compilation. Also you probably want to wait until `rollup-plugin-vue` support vue-next.
2020-02-25T21:20:54
2020-02-25T21:20:54
{}
MEMBER
vuejs
core
591,671,055
674
yyx990803
@jods fyi: e9024bf
2020-02-26T22:12:31
2020-02-26T22:12:31
{ "+1": 1 }
MEMBER
vuejs
core
591,736,239
721
yyyanghj
How about this ? ```ts import AuthenticateUser from "./somewhere/authenticateUser.ts" import Store from "./somewhere/Store.ts" const createAuthenticateUser = ( authenticateUser = AuthenticateUser ) => ({ name: 'MyComponent', setup(props, { root }){ return { authenticate: authenticateUser( Stor...
2020-02-27T01:50:25
2020-02-27T01:50:25
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
587,932,079
739
exodusanto
My fault... missing @vue/compiler-sfc bump ¯\_(ツ)_/¯
2020-02-18T22:18:15
2020-02-18T22:18:15
{}
NONE
vuejs
core
588,436,864
674
jods4
I'm really wishing for a `shallowRef` in Vue core as well. @yyx990803 is it possible? Typical use case is to store immutable/non-reactive (big) arrays or (deep) objects (for perf). E.g. if you want to display a large list and plan on setting the ref to a new array to avoid watching all array indexes (ties in with yo...
2020-02-19T20:36:09
2020-02-19T20:36:09
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
588,798,324
745
lmiller1990
I've been playing around with a custom renderer (well actually, modified version of dom renderer) for Vue Test Utils - let's call it `test-renderer`. The main goal is to some extra functionality to stub out components. Nothing useful public yet, but my main takeaways have been: - start by copy-pasting the `nodeOps` ...
2020-02-20T08:58:09
2020-02-20T08:58:17
{}
MEMBER
vuejs
core
589,618,388
749
yyx990803
Maybe `class` and `style` should be special cased even when no props are declared.
2020-02-21T11:39:16
2020-02-21T11:39:27
{}
MEMBER
vuejs
core
589,713,230
758
yyx990803
Could you please can make a new PR based on my commit
2020-02-21T15:53:44
2020-02-21T15:53:44
{}
MEMBER
vuejs
core
590,764,630
773
underfin
https://github.com/vuejs/vue-next/commit/3375687df5e7751d3df69190c99f4ce13b8f1993
2020-02-25T09:17:51
2020-02-25T09:17:51
{}
MEMBER
vuejs
core
590,994,366
772
jods4
@yyx990803 seems to work in simple cases. My refs still don't work in a slot, is that expected? Repro here: https://codesandbox.io/s/v-model-decomposed-camel-case-gp8c5 EDIT: I thought that it might be related to #766 but it doesn't seem to fix it.
2020-02-25T18:19:30
2020-02-25T18:20:38
{}
CONTRIBUTOR
vuejs
core
591,378,012
782
hareku
It worked out too when I remove the panel component from `Profile.vue`.
2020-02-26T11:25:18
2020-02-26T12:16:38
{}
CONTRIBUTOR
vuejs
core
585,863,445
721
relief-melone
I extended my example a little bit and hope that adds some clarification. Basically this would enable us to replace basically anything in our component in particular functions. With provide and inject if I understand correctly this would not be possible if we don't wrap it.
2020-02-13T17:04:26
2020-02-13T17:04:26
{}
NONE
vuejs
core
589,599,211
749
underfin
https://github.com/vuejs/rfcs/pull/92. If components with no props declaration, will be not implicit fallthrough attrs.
2020-02-21T10:41:14
2020-02-21T10:41:14
{ "+1": 1 }
MEMBER
vuejs
core
589,703,731
758
guaijie
a=[1,3,4,5,6] a.length=2 effect will triggered for [4,5,6] unrelatived effects will not triggered
2020-02-21T15:32:30
2020-02-21T15:32:30
{}
CONTRIBUTOR
vuejs
core
591,171,738
759
yyx990803
That's a good catch. I think ref value unwrapping should happen in its creation signature - see d4c6957
2020-02-26T00:45:19
2020-02-26T00:45:19
{}
MEMBER
vuejs
core
589,862,396
737
jods4
This is tricky stuff, there are no perfect answer for all cases. I would set some design principles for a successful API: 1. have a simple, clear, coherent mental model; 2. be extensible: allow full control when required; 3. easily support common cases out of the box with little ceremony. Magically unwrapping ...
2020-02-21T22:23:25
2020-02-21T22:23:25
{ "+1": 4 }
CONTRIBUTOR
vuejs
core
591,503,840
783
yyx990803
I think a dedicated object here is technically safer, since `EMPTY_OBJ` is indeed used elsewhere and has a slight chance to be returned in a watcher getter. I know it is highly unlikely, but if it does happen it can be very hard to figure out why.
2020-02-26T16:03:17
2020-02-26T16:03:17
{}
MEMBER
vuejs
core
633,652,773
1,227
yyx990803
@RobbinBaauw this would require a fresh ctx object and spreading everything on every render - which comes with its own costs.
2020-05-25T16:58:57
2020-05-25T16:58:57
{}
MEMBER
vuejs
core
633,738,066
1,238
yyx990803
This is expected behavior. Empty string for Boolean props is casted to `true`, because when you write `<Comp foo/>`, the props are compiled into `{ foo: '' }`. Casting behavior also depends on the order of the type you specified.
2020-05-25T23:05:46
2020-05-25T23:05:46
{ "+1": 1 }
MEMBER
vuejs
core
634,412,905
1,241
KaelWD
Ah I see the AST is completely different now, vue-template-compiler parses v-slot to scopedSlots instead of keeping the template element. > Is it difficult to switch to different slot names? It's used for arbitrary property lookup on objects, so `{ foo: { bar: 'baz' } }` can be accessed with `v-slot:item.foo.bar...
2020-05-27T03:56:23
2020-05-27T03:56:23
{}
CONTRIBUTOR
vuejs
core
634,509,837
1,242
underfin
This maybe caused by event compat in between pc and moblie.Either way it's not a bug for vue.
2020-05-27T08:25:55
2020-05-27T08:25:55
{}
MEMBER
vuejs
core
634,524,263
1,242
posva
Please, explains the actions you do, what you expect to see compared to what you see **like the issue I linked to**. As @underfin said, this is very likely to be a normal behavior. You can try reproducing it by doing plain javascript and adding the events that vue add
2020-05-27T08:54:25
2020-05-27T08:54:25
{}
MEMBER
vuejs
core
635,145,276
1,248
underfin
Export that maybe caused some error when the user user it and chaneg it. This will add the cost of our maintain and maybe be this will have break change in the future.So avoid use it.
2020-05-28T06:54:29
2020-05-28T06:54:29
{}
MEMBER
vuejs
core
635,259,545
1,248
zzzz-Z
> You should be injecting or emitting, accessing the internalComponent is not a good practice in general. Injection is top-down for example a form component and I've internally defined a validation method that can't be solved by injection when the user wants to use it And we also get instance.ctx when we add r...
2020-05-28T10:34:24
2020-05-28T10:34:24
{}
CONTRIBUTOR
vuejs
core
636,428,480
1,268
underfin
Thanks for this pr. But we can't warp some tags with user provider,like this case.And if we do it, should process it in complier time instead of runtime. In fact,we should avoid stringfy some node which cause error when use `innnerHtml` , eg. table related nodes.
2020-05-31T06:14:15
2020-05-31T06:16:21
{}
MEMBER
vuejs
core
636,428,732
1,268
shengxinjing
thanks for reply , aviod compiler transform table node to staticNode maybe better, I'll try to submit the code again later. thanks
2020-05-31T06:17:43
2020-05-31T06:17:43
{}
CONTRIBUTOR
vuejs
core
636,430,304
1,268
shengxinjing
> > compiler is better for code organization > > maybe runtimer is better for perf > > No.Because we also consider ssr.If we wrap some tags only in runtime-dom.It will cause hydration error. we wrap table element and get firstChild by depth for return ,we also has same dom tree in ssr
2020-05-31T06:39:33
2020-05-31T06:39:33
{}
CONTRIBUTOR
vuejs
core
636,720,029
1,216
dependabot-preview[bot]
Superseded by #1277.
2020-06-01T09:07:19
2020-06-01T09:07:19
{}
CONTRIBUTOR
vuejs
core
634,596,650
1,235
ozguruysal
@underfin thanks for looking into this. Not sure I understand why I would try to teleport the content if I have to add it to the target element too. Maybe `<teleport>` should be rendered client side only as in [PortalVue](https://github.com/LinusBorg/portal-vue) by wrapping it in something like `<client-only>`? E...
2020-05-27T11:23:33
2020-05-27T11:48:50
{}
NONE
vuejs
core
635,145,386
1,249
LinusBorg
FWIW you can make it more consise with ES6 already. ```javascript const r1 = reactive({ r1: 1 }) const r2 = reactive({ r2: 2 }) const r3 = reactive({ r3: 3 }) export default { setup() { return { ...Object.assign(toRefs(r1), toRefs(r2), toRefs(r3)) } }, } ```
2020-05-28T06:54:43
2020-05-28T06:54:43
{}
MEMBER
vuejs
core
636,325,722
1,106
yyx990803
Will merge first thing next week!
2020-05-30T12:40:14
2020-05-30T12:40:14
{ "hooray": 10 }
MEMBER
vuejs
core
636,671,741
1,271
underfin
@pikax thanks a lot!
2020-06-01T07:43:34
2020-06-01T07:43:34
{ "+1": 1 }
MEMBER
vuejs
core
635,040,870
1,242
allowing
1. open the [https://jsfiddle.net/3L6y0wh5/show](https://jsfiddle.net/3L6y0wh5/show) 1. Set to phone mode. 1. click these items 1. if you can see a number in console, that is expected.
2020-05-28T01:40:19
2020-05-28T01:40:19
{}
NONE
vuejs
core
635,950,019
1,259
pikax
`ts-jest` doesn't like optional chaining
2020-05-29T12:39:13
2020-05-29T12:39:13
{}
MEMBER
vuejs
core
635,990,409
1,227
aztalbot
@basvanmeurs I meant in the context of a single instance, since setup will run once per instance and the code in that example is only trying to determine where to find that value for the lifetime of that specific instance. What I was going for is that we know all the keys we need to reference based on the template, so ...
2020-05-29T14:05:05
2020-05-29T14:18:29
{}
CONTRIBUTOR
vuejs
core
636,505,008
1,270
yyx990803
Please use https://github.com/vuejs/rfcs for this type of discussions. The short answer is: no, because `ref`, `reactive` and `watch` all do fundamentally differently things and you will need to understand them and distinguish them for their best use cases. Hiding them under a single magic function does not reduce t...
2020-05-31T17:53:10
2020-05-31T17:53:10
{ "+1": 1 }
MEMBER
vuejs
core
636,581,424
1,271
underfin
![image](https://user-images.githubusercontent.com/14008915/83370977-8ad7cb80-a3f3-11ea-9d3f-bbf0d66c68ea.png) Run single test is ok...
2020-06-01T02:35:37
2020-06-01T02:35:37
{}
MEMBER
vuejs
core
633,246,418
1,228
underfin
You can remove `isolatedModules ` option (look like this is necessary ) and add typescript@3.8.3(keep the same version with vue-core).
2020-05-24T15:18:03
2020-05-24T15:18:03
{}
MEMBER
vuejs
core
633,855,662
1,220
zhangenming
@sionzeecz thanks @Justineo I think they are the same cause of confusion and there should be a better name to distinguish them
2020-05-26T07:22:38
2020-05-26T07:22:53
{}
CONTRIBUTOR
vuejs
core
634,609,009
1,235
underfin
Yeah.The `Teleport ` (Portal) and their ssr is support by core.
2020-05-27T11:52:04
2020-05-27T11:52:04
{}
MEMBER
vuejs
core
634,623,717
1,241
b-strauss
Vuetify does this on their table component in combination with dynamic slot names. https://vuetifyjs.com/en/components/data-tables/#api ```js var items = [ { firstname: 'foo', lastname: 'bar', }, ]; ``` ```html <v-data-table :items="items"> <!-- this slot only applies to the firstname colu...
2020-05-27T12:23:12
2020-05-27T12:26:01
{}
NONE
vuejs
core
635,189,343
1,247
basvanmeurs
Please don't merge this pull request yet. I'd like to do some further analysis on the performance of creating new component instances, memory usage and optimizer behavior.
2020-05-28T08:12:26
2020-05-28T08:12:26
{}
CONTRIBUTOR
vuejs
core
635,292,431
1,248
pikax
not sure what you trying to do. > for example a form component and I've internally defined a validation method that can't be solved by injection when the user wants to use it As a good practice the parent(user?) can only interact with the child(form component) through props. > Or what the ref of the component...
2020-05-28T11:53:07
2020-05-28T11:53:07
{}
MEMBER
vuejs
core
635,937,121
1,257
sionzee
@jacekkarczmarczyk uh, I see, the first dot is used as decimal point and the second one for a function call. More understandable for me looks `String(10)` than `10..toString()`. Anyway thank you for a lesson :)
2020-05-29T12:07:56
2020-05-29T12:07:56
{}
NONE
vuejs
core
636,930,546
1,282
posva
Thank you but as said in #1280 and #1279, this is less readable. There is also no need to open 3 pull requests for the same thing
2020-06-01T15:42:26
2020-06-01T15:42:26
{}
MEMBER
vuejs
core
633,267,619
1,197
CyberAP
@yyx990803 there's one problem remaining still that I'm not sure which way is exactly the best to tackle it. SSR compiler would produce optimized code only for `renderToString`, but not for `renderToStream`, since runtime helpers exist only for the former. I thought of two ways dealing with it: a compiler setting or...
2020-05-24T17:57:41
2020-05-24T17:57:41
{}
CONTRIBUTOR
vuejs
core
633,348,586
1,229
allowing
[https://github.com/allowing/tem-vue-next](https://github.com/allowing/tem-vue-next)
2020-05-25T02:42:27
2020-05-25T02:42:27
{}
NONE
vuejs
core
635,064,924
1,246
guaijie
```js it.only('should observe inherited property accessors', () => { let dummy, parentDummy, hiddenValue: any const obj = reactive<{ prop?: number }>({}) const parent = reactive({ set prop(value) { hiddenValue = value }, get prop() { return hiddenValue } ...
2020-05-28T02:55:40
2020-05-28T13:43:03
{}
CONTRIBUTOR
vuejs
core
635,968,855
1,247
basvanmeurs
I changed some things in the original idea and did some extensive performance testing, comparing the current vue-next version with this PR. The results are further below, but most importantly they show that instance proxy performance in component instance creation has become about 15% slower (because some functions and...
2020-05-29T13:20:51
2020-05-29T13:22:08
{}
CONTRIBUTOR
vuejs
core
636,367,393
1,247
ZhangJian-3ti
Based on the data you provide, seems not worthy in the real world cases.
2020-05-30T18:27:27
2020-05-30T18:27:27
{}
CONTRIBUTOR
vuejs
core
633,518,773
1,220
sionzee
@Justineo I think he doesn't want to change the public API. He is pointing to the line: ``` const effect = createReactiveEffect(fn, options) ``` Because the function name is also called `effect` it looks like tail-recursive call. Solution should be to use different variable name for the `effect`, eg. `reacti...
2020-05-25T11:09:15
2020-05-25T11:11:15
{}
NONE
vuejs
core
634,631,515
1,227
aztalbot
These all seem like good solutions. Just an observation: some of the optimizations end up adding adding arguments to the render function call as well as fields to the instance. The _cache is already an existing case of doing this, since the only place to cache data in the render function is on the instance. This makes ...
2020-05-27T12:37:57
2020-05-27T14:16:37
{}
CONTRIBUTOR
vuejs
core
635,197,048
1,247
pikax
> Please don't merge this pull request yet You mark it as **WIP** or move it to draft
2020-05-28T08:26:48
2020-05-28T08:26:48
{}
MEMBER
vuejs
core
636,429,045
1,268
shengxinjing
compiler is better for code organization maybe runtime is better for perf
2020-05-31T06:22:39
2020-05-31T12:13:47
{}
CONTRIBUTOR
vuejs
core
636,713,633
1,251
dependabot-preview[bot]
Superseded by #1272.
2020-06-01T08:57:07
2020-06-01T08:57:07
{}
CONTRIBUTOR
vuejs
core
636,922,430
1,276
underfin
![image](https://user-images.githubusercontent.com/14008915/83424482-0884f100-a45f-11ea-963a-a75d27e06569.png) That can work for me.My operation system is mac.
2020-06-01T15:26:12
2020-06-01T15:27:04
{}
MEMBER
vuejs
core
636,927,310
1,280
posva
Thanks but these are not even included in the final build and it's less readable
2020-06-01T15:36:05
2020-06-01T15:36:05
{}
MEMBER
vuejs
core
633,976,151
1,237
rigor789
@pikax I believe this only affects the monorepo itself managed by Yarn workspaces - where npm wouldn't work correctly.
2020-05-26T11:49:24
2020-05-26T11:49:24
{}
CONTRIBUTOR
vuejs
core
634,118,644
1,227
basvanmeurs
Notice that this needs some work, as this change breaks a lot of unit tests. These failures seem to be false positives as they use a compiler snapshot as output, giving false positives. @yyx990803 are you interested in implementing this solution? Before I continue to fix the unit tests..
2020-05-26T16:02:02
2020-05-26T16:02:02
{}
CONTRIBUTOR
vuejs
core
634,519,572
1,242
posva
I don't follow... Can you make it clear by following the template, example: https://github.com/vuejs/vue-next/issues/906
2020-05-27T08:45:18
2020-05-27T08:45:28
{}
MEMBER
vuejs
core
634,527,355
1,242
allowing
[https://jsfiddle.net/3L6y0wh5/show](https://jsfiddle.net/3L6y0wh5/show) This link can reproduce the phenomenon I described. Set to phone mode. This should not be normal.
2020-05-27T09:00:07
2020-05-27T09:00:07
{}
NONE
vuejs
core
635,928,720
1,257
sionzee
@marcusball, `toString()` is not available on all types, try type `10.toString()` into console. Proper way is to use String. ```javascript toString() { return String(value) } ``` But is worth to check what does transpiled string interpolation. Maybe it does it automatically. ---- I don't think it is n...
2020-05-29T11:46:52
2020-05-29T11:57:07
{ "+1": 2, "heart": 1 }
NONE
vuejs
core
636,444,568
1,268
underfin
Yeah.I realizi it.So call back it.
2020-05-31T09:19:16
2020-05-31T09:19:16
{}
MEMBER
vuejs
core
636,721,301
1,277
dependabot-preview[bot]
One of your CI runs failed on this pull request, so Dependabot won't merge it. - [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/5500?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) Dependabot will still automatically merge this pull request if you amend it and your test...
2020-06-01T09:09:14
2020-06-01T09:09:14
{}
CONTRIBUTOR
vuejs
core
633,147,897
1,195
frangio
I'm not really sure what test I should add. This type is an internal utility so it's not exported from the index file.
2020-05-23T22:19:39
2020-05-23T22:19:39
{}
NONE
vuejs
core
634,117,200
1,227
basvanmeurs
When thinking of a solution, I realise that dynamic props, context and globals really complicate things. I personally think that developers shouldn't use these features in vue3, but stick to the setup vars and defined props, and use the composition api to add globals. Same goes for using $emit etc directly from a templ...
2020-05-26T15:59:36
2020-05-26T15:59:36
{}
CONTRIBUTOR
vuejs
core
634,515,403
1,242
allowing
I think `touchend` changed the state, and then re-rendered the view, causing the` click` event listener to rebind, before and after re-rendering are two different event handlers. This situation occurs in Android phone and chrome phone views. The iPhone is performing normally.
2020-05-27T08:37:10
2020-05-27T08:37:10
{}
NONE
vuejs
core
635,207,298
1,248
pikax
> What should I do when I use setup to dye back to a renderFn and I want the user to be able to access my internal methods? You should be injecting or emitting, accessing the internalComponent is not a good practice in general. > And I see that keepalive USES this property as well Keep alive is an internal com...
2020-05-28T08:46:13
2020-05-28T08:46:13
{}
MEMBER
vuejs
core
635,210,074
1,246
zhangenming
调试响应式代码好头大哦 一层一层的 都是各种代理getter 一会脑袋就凌乱了
2020-05-28T08:51:43
2020-05-28T08:51:43
{}
CONTRIBUTOR
vuejs
core
635,211,172
1,244
dependabot-preview[bot]
Superseded by #1253.
2020-05-28T08:53:51
2020-05-28T08:53:51
{}
CONTRIBUTOR
vuejs
core
635,934,235
1,257
jacekkarczmarczyk
@sionzeecz > try type 10.toString() into console. ![image](https://user-images.githubusercontent.com/15625235/83257491-c9337780-a1b4-11ea-98b8-c8f118fbe73d.png)
2020-05-29T12:00:56
2020-05-29T12:00:56
{ "+1": 3 }
CONTRIBUTOR
vuejs
core
633,953,043
1,237
pikax
`vue-next` should be able to be installed by `npm`, package manager is user choice.
2020-05-26T10:52:55
2020-05-26T10:52:55
{}
MEMBER
vuejs
core
634,522,276
1,242
allowing
![image](https://user-images.githubusercontent.com/20262949/82998261-16d7a500-a03a-11ea-9d09-afda8519c813.png) Only responded once to click
2020-05-27T08:50:36
2020-05-27T08:50:36
{}
NONE
vuejs
core
635,340,205
1,248
yyx990803
Because it’s internal and you shouldn’t use it.
2020-05-28T13:10:20
2020-05-28T13:10:20
{}
MEMBER
vuejs
core
636,714,155
1,253
dependabot-preview[bot]
Superseded by #1274.
2020-06-01T08:57:57
2020-06-01T08:57:57
{}
CONTRIBUTOR
vuejs
core
633,347,412
1,229
underfin
Can you provider an repo?
2020-05-25T02:37:00
2020-05-25T02:37:00
{}
MEMBER
vuejs
core
633,343,607
1,195
runkids
When i run script ```bash tsc --target ESNext --module ES6 --outDir esm ``` I was seeing this error too. ``` > tsc --target ESNext --module ES6 --outDir esm node_modules/@vue/runtime-core/dist/runtime-core.d.ts:437:20 - error TS2344: Type 'Function & T[key]["get"]' does not satisfy the constraint '(...args: an...
2020-05-25T02:18:02
2020-05-25T05:43:53
{}
NONE
vuejs
core
633,614,977
1,228
sapphi-red
The same error was found after changing typescript to v3.8.3. Also I am not in trouble with this error. I thought it would be better if these error were not shown even if `isolatedModules` were turned on. Maybe its more like a feature request than a bug report.
2020-05-25T15:08:30
2020-05-25T15:08:30
{}
CONTRIBUTOR