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 | 615,936,425 | 989 | aztalbot | Right, I saw it being used in runtime-dom, so I thought it was ok to use. I also thought the planned support for IE11, mostly due to Proxies, would be via a build-time flag, so poly-filling for IE support should all only need to happen when that flag is set. Maybe `startsWith` isn't an important enough change to be inc... | 2020-04-18T20:00:45 | 2020-04-18T21:38:19 | {} | CONTRIBUTOR |
vuejs | core | 617,956,252 | 1,031 | yyx990803 | Thanks for the PR, but the code in question is kept like that intentionally because the `Dep` type abstraction doesn't help in that context. | 2020-04-22T18:35:45 | 2020-04-22T18:35:45 | {} | MEMBER |
vuejs | core | 614,990,958 | 972 | 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-04-17T01:47:46 | 2020-04-17T01:47:46 | {} | CONTRIBUTOR |
vuejs | core | 615,015,897 | 973 | whhjdi | writing | 2020-04-17T03:21:07 | 2020-04-17T03:21:07 | {} | NONE |
vuejs | core | 616,038,682 | 963 | himself65 | I think this cause by type loop | 2020-04-19T05:27:33 | 2020-04-19T05:27:33 | {} | CONTRIBUTOR |
vuejs | core | 616,800,766 | 991 | yyx990803 | Thanks a lot for the PR, although like @dsonet said, I'm not sure if this is a worthwhile trade-off. Typed Arrays are a relatively niche use case but these changes adds both non-tree-shakable payload and runtime overhead to the vast majority of the users who don't need them.
Also, typed arrays are usually used in pe... | 2020-04-20T20:48:24 | 2020-04-20T20:48:24 | {
"+1": 3
} | MEMBER |
vuejs | core | 616,825,585 | 994 | jods4 | I think it's good etiquette in good ol' pure JS libraries to leave things as they found it when they have a `destroy` function. So although it's not helping in this particular case, I'm not surprised by behavior.
I worked around it in Vue already, in a very ninja-way (= not great, very hacky 🤕).
It's also possible... | 2020-04-20T21:41:28 | 2020-04-20T21:41:28 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 617,130,701 | 1,011 | yyx990803 | This is all working as intended.
The source can only be a bare ref, not a reactive object.
Deep is needed if you want to watch nested mutations in addition to the return value's identity. | 2020-04-21T11:47:41 | 2020-04-21T11:47:41 | {} | MEMBER |
vuejs | core | 617,554,661 | 1,017 | yyx990803 | https://github.com/vuejs/rfcs/blob/master/active-rfcs/0031-attr-fallthrough.md | 2020-04-22T05:12:47 | 2020-04-22T05:12:47 | {} | MEMBER |
vuejs | core | 612,817,947 | 952 | LinusBorg | That sounds like a good idea, will see how big of an effort that would require to actually make customizable. | 2020-04-13T09:03:09 | 2020-04-13T09:03:09 | {
"heart": 1
} | MEMBER |
vuejs | core | 613,102,597 | 909 | yyx990803 | This is reverted because I misread my own explanation. If you are building a user-facing renderer, you should have both `@vue/reactivity` and `@vue/runtime-core` in your dependencies, and be able to import `effect` from `@vue/reactivity`.
The sentence
> The standalone build should not be used alongside a pre-bund... | 2020-04-13T21:17:28 | 2020-04-13T21:17:28 | {} | MEMBER |
vuejs | core | 613,393,402 | 961 | posva | @CyberAP https://github.com/vuejs/vue-next/pull/909#issuecomment-613102597 | 2020-04-14T11:45:39 | 2020-04-14T11:45:39 | {} | MEMBER |
vuejs | core | 615,924,025 | 989 | aztalbot | @rigor789 thanks for that. I should have included the benchmark I had, but I actually like the tool you linked better. My assumption is that in these cases, there will most often be small strings that don't start with the prefix. So here is a modified [benchmark](https://perf.link/#eyJpZCI6ImRneDJic3RmdGM5IiwidGl0bGUiO... | 2020-04-18T18:42:07 | 2020-04-18T18:57:55 | {} | CONTRIBUTOR |
vuejs | core | 616,420,373 | 999 | pikax | As far as I know when you return render function from setup, it will re-render every time creating a new component, but you can simulate the render by creating the render blocks your self [here](https://codesandbox.io/s/jolly-payne-gm0em?file=/index.html)
```ts
// NOTE HACK
const App = {
setup() {
... | 2020-04-20T09:16:55 | 2020-04-20T09:39:32 | {} | MEMBER |
vuejs | core | 617,962,698 | 1,027 | yyx990803 | I don't think this is the correct fix - see 7d0ab339 | 2020-04-22T18:47:47 | 2020-04-22T18:47:47 | {} | MEMBER |
vuejs | core | 614,085,642 | 579 | yyx990803 | Can you remove the formatting changes from this PR? | 2020-04-15T14:49:44 | 2020-04-15T14:49:44 | {
"+1": 1
} | MEMBER |
vuejs | core | 615,538,905 | 985 | Justineo | Please **DO NOT** abuse pull requests. Do experiments in your own repo. Thanks. | 2020-04-18T02:07:18 | 2020-04-18T02:07:18 | {} | MEMBER |
vuejs | core | 615,931,204 | 989 | posva | startsWith is not supported on IE though | 2020-04-18T19:21:54 | 2020-04-18T19:21:54 | {
"eyes": 2
} | MEMBER |
vuejs | core | 616,665,113 | 1,001 | yyx990803 | @aztalbot yes, in this case the warning should nudge the user to add the emitted event to the `emits` option. | 2020-04-20T16:28:02 | 2020-04-20T16:28:02 | {} | MEMBER |
vuejs | core | 617,591,384 | 1,020 | wjw99830 | ```js
h('div', {
onClick: () => console.log('click')
})
``` | 2020-04-22T07:02:21 | 2020-04-22T07:02:21 | {} | NONE |
vuejs | core | 614,067,161 | 916 | jods4 | No, there is not. I checked when opening the issue, which would have been trivial otherwise.
You'd have to monkeypatch `stopImmediatePropagation` on every event.
Maybe it's a bit excessive for something that has a very narrow use case?
The current behavior is unintuitive and I got caught off guard by it. Took me... | 2020-04-15T14:17:04 | 2020-04-15T14:17:04 | {} | CONTRIBUTOR |
vuejs | core | 614,092,251 | 579 | pikax | formatting fixed after merging https://github.com/vuejs/vue-next/commit/1068212cb2c3e8be89b11fc677a963f94db23708 | 2020-04-15T15:00:39 | 2020-04-15T15:00:39 | {} | MEMBER |
vuejs | core | 615,922,481 | 989 | rigor789 | [Here's a perf test for both ](https://perf.link/#eyJpZCI6ImlqdWF6ZGU4NWt3IiwidGl0bGUiOiJpbmRleE9mID09PSAwIG9yIHN0YXJ0c1dpdGgiLCJiZWZvcmUiOiJjb25zdCBzdHJpbmdzID0gW1xuICAndXBkYXRlOicsXG4gICdsYXRlcnVwZGF0ZTonLCBcbiAgJzlOSEhIR3p5aVIyRXh6dlZISjRzJywgXG4gICd1cEhlaGdwZmhWc2xxbWE0MkVjRG9IZGF0ZTp1cGRhdGU6JyxcbidIZWhncGZoVnNscW... | 2020-04-18T18:33:36 | 2020-04-18T18:33:36 | {} | CONTRIBUTOR |
vuejs | core | 616,537,416 | 1,001 | aztalbot | I wonder if the intended way to resolve that warning would be for the parent component of the fragment to declare "btn-clicked" in `emits` or to do `v-bind="$attrs"` on one of the children. It prevents the warning because it parses it out of `attrs`. So maybe the error should be improved to direct the user to either ad... | 2020-04-20T13:01:19 | 2020-04-20T15:18:21 | {} | CONTRIBUTOR |
vuejs | core | 616,773,969 | 987 | yyx990803 | If you expect it to just throw, what's the point of adding `app.config.errorHandler` in this case then? | 2020-04-20T19:53:46 | 2020-04-20T19:54:08 | {} | MEMBER |
vuejs | core | 616,795,620 | 987 | yyx990803 | My point is in your test setup you don't need the `errorHandler` at all - then it will just throw as expected. | 2020-04-20T20:38:22 | 2020-04-20T20:38:22 | {} | MEMBER |
vuejs | core | 616,925,162 | 1,008 | 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-04-21T03:10:01 | 2020-04-21T03:10:01 | {} | CONTRIBUTOR |
vuejs | core | 617,638,400 | 1,023 | yyx990803 | Fixed, but it's still better to name the functional component. | 2020-04-22T08:39:42 | 2020-04-22T08:39:42 | {} | MEMBER |
vuejs | core | 614,650,636 | 969 | yyx990803 | That's correct. Only built-in symbol properties are returned raw. Users may expect reactivity on custom symbol properties. | 2020-04-16T13:24:42 | 2020-04-16T13:24:42 | {
"+1": 1
} | MEMBER |
vuejs | core | 617,664,563 | 1,019 | John0King | @yyx990803 try a new Vue project, I find that the Vetur only support object style of vue for tag complete, and property complate and has **no support for event** ,
I think may be Vetur use some pattern match tech, and there on such pattern for $emit.
and by using analyze ts class metadata , then I believe th... | 2020-04-22T09:28:50 | 2020-04-22T09:28:50 | {} | NONE |
vuejs | core | 614,057,867 | 916 | LinusBorg | Hm. Is there any way to find out wether an event's `stopImmediatePropagation` has been called?
There's `event.defaultPrevented` for `event.preventDefault()` but I'm not aware of anything similar for `stopImmediatePropagation`.
So should we monkeypatch the method of the event to be able to track it? I don't really... | 2020-04-15T13:59:57 | 2020-04-15T13:59:57 | {} | MEMBER |
vuejs | core | 614,445,319 | 966 | 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-04-16T06:38:44 | 2020-04-16T06:38:44 | {} | CONTRIBUTOR |
vuejs | core | 615,167,018 | 681 | jiangying000 | Is this fixed by 0764c33d3da8c06d472893a4e451e33394726a42? | 2020-04-17T10:18:34 | 2020-04-17T10:18:34 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 615,235,937 | 982 | yyx990803 | Ugh, why does GitHub forget the preference and reverted back to normal merge? This has happened a few times lately. | 2020-04-17T13:11:33 | 2020-04-17T13:11:33 | {} | MEMBER |
vuejs | core | 615,284,492 | 681 | jonaskuske | Yep, seems like `alpha.11` fixed this already 👍🏻 | 2020-04-17T14:43:30 | 2020-04-17T14:43:30 | {} | CONTRIBUTOR |
vuejs | core | 616,769,226 | 989 | yyx990803 | Good discussions here. I originally was thinking to use `indexOf` everywhere in runtime packages so that we don't need to polyfill it in IE, but I think that has a few drawbacks, namely slightly worse performance in modern engines and a constraint that is somewhat cumbersome to enforce via tooling (I tried to have diff... | 2020-04-20T19:44:01 | 2020-04-20T19:44:01 | {
"+1": 3
} | MEMBER |
vuejs | core | 616,907,166 | 999 | yyx990803 | btw, it's better to use `shallowRef` for Three.js objects to avoid observing them (since you are creating new vectors on each update and not mutating them) | 2020-04-21T02:08:23 | 2020-04-21T02:08:23 | {
"heart": 1
} | MEMBER |
vuejs | core | 617,140,618 | 1,014 | yyx990803 | Duplicate of #963 | 2020-04-21T12:10:40 | 2020-04-21T12:10:40 | {} | MEMBER |
vuejs | core | 617,994,739 | 1,025 | yyx990803 | In Vue 2 these attributes are rendered. It's best to keep the behavior consistent. Users can also potentially bind a custom attribute with these names. | 2020-04-22T19:42:46 | 2020-04-22T19:42:46 | {} | MEMBER |
vuejs | core | 687,883,438 | 1,790 | jods4 | I'm gonna add one more reason to be very careful here!
In an ideal world, everything is pure (without side-effects), especially render functions.
Reality isn't so and look no further than core Vue itself for an example:
Layout animations are typically done by looking at changes across renders and trigger the require... | 2020-09-06T19:49:34 | 2020-09-06T19:49:34 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 687,892,178 | 1,790 | CyberAP | This change actually introduces a lot of pain when working with renderless provider components which are still viable in Vue 3. Provider components generally wrap your whole app and do not render anything other than the default slot. If I understand this correctly updating provider would cause a whole app VNode tree to... | 2020-09-06T20:24:52 | 2020-09-06T20:25:22 | {} | CONTRIBUTOR |
vuejs | core | 689,474,789 | 2,077 | posva | This has been discussed multiple times: https://github.com/vuejs/vue/issues/6259 https://github.com/vuejs/vue/issues/8028 https://github.com/vuejs/vue/issues/10487.
This is probably worth going through an RFC by comparing existing solutions with include, exclude and max | 2020-09-09T10:30:49 | 2020-09-09T10:30:49 | {} | MEMBER |
vuejs | core | 690,019,775 | 2,086 | 07akioni | > Sorry, I provided the wrong link, it's here: [5f40539](https://github.com/vuejs/vue-next/commit/5f4053967cb61620d3dd27518f571166d7b5ec8f)
thanks | 2020-09-10T06:31:12 | 2020-09-10T06:31:12 | {} | CONTRIBUTOR |
vuejs | core | 690,035,308 | 2,087 | HcySunYang | What do you mean? do you need https://v3.vuejs.org/api/options-lifecycle-hooks.html#beforeunmount ? | 2020-09-10T07:05:20 | 2020-09-10T07:05:20 | {} | MEMBER |
vuejs | core | 691,334,194 | 2,099 | yyx990803 | @CyberAP renderless component will work without transition. | 2020-09-11T22:12:27 | 2020-09-11T22:12:27 | {} | MEMBER |
vuejs | core | 691,655,133 | 2,108 | KaelWD | This was a problem in v2 as well for libraries using `Vue.extend()`, there's some discussion about it in https://github.com/vuetifyjs/vuetify/discussions/4068 | 2020-09-13T10:47:06 | 2020-09-13T10:47:06 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 687,911,348 | 2,057 | an-sh | On Sun, 2020-09-06 at 01:05 -0700, Eduardo San Martin Morote wrote:
> Closed #2057.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.
Looks like this one is a partial duplicate, it doesn't cover a case
with a different standalone ref beh... | 2020-09-06T21:51:52 | 2020-09-06T21:51:52 | {} | NONE |
vuejs | core | 688,183,155 | 2,064 | znck | I am checking. | 2020-09-07T09:06:10 | 2020-09-07T09:06:10 | {} | MEMBER |
vuejs | core | 690,034,344 | 2,083 | posva | This is expected, when calling ref on a ref, it doesn't wrap an extra ref layer on it so you can write foo.value instead of foo.value.value | 2020-09-10T07:03:32 | 2020-09-10T07:03:32 | {} | MEMBER |
vuejs | core | 690,108,891 | 2,082 | posva | This breaking change went through an RFC and is documented https://v3.vuejs.org/guide/migration/v-model.html#_3-x-syntax
In short, name your prop `modelValue` to use `v-model` | 2020-09-10T09:24:23 | 2020-09-10T09:24:23 | {} | MEMBER |
vuejs | core | 690,891,306 | 2,097 | lawvs | This is one way to implement the same features in vue3. No need to use a new app.
~~Sorry for using jsx~~
<details>
```tsx
// Message HOC
import { Teleport, defineComponent, provide, ref } from 'vue'
const Message = ({ open, text }) => (
<Teleport to="body">{open && <div className="modal">{text}</div>}</... | 2020-09-11T05:52:56 | 2020-09-11T06:08:26 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 691,511,768 | 2,080 | sionzee | For me it is happening the same but instead of comment at my first position is "v-if" condition what have "false" value. Which results in `<!--v-if-->` comment. | 2020-09-12T16:18:25 | 2020-09-12T16:18:25 | {} | NONE |
vuejs | core | 691,623,763 | 2,105 | luthfimasruri | Maybe it's the typescript compiler that didn't understand Vue syntax, | 2020-09-13T07:00:58 | 2020-09-13T07:00:58 | {} | NONE |
vuejs | core | 687,882,002 | 1,790 | jods4 | I read @yyx990803 comments in #1181, but I just don't get it.
He says correctness is more important than optimizations and I wholly agree with that.
But what is the correctness issue here?
If a specific prop is not a dependency of rendering (there can be many good reasons for that), I don't see what issue could... | 2020-09-06T19:43:17 | 2020-09-06T19:43:17 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 690,219,423 | 2,093 | posva | This is expected, it's necessary for the watcher to collect dependencies synchronously. As you mentioned, you can still read properties outside of the asynchronous code (or before an `await`) to make it work. Maybe worth documenting in the API, will share with the team | 2020-09-10T11:56:03 | 2020-09-10T11:56:03 | {} | MEMBER |
vuejs | core | 691,655,368 | 2,108 | frei-x | > This was a problem in v2 as well for libraries using `Vue.extend()`, there's some discussion about it in [vuetifyjs/vuetify#4068](https://github.com/vuetifyjs/vuetify/discussions/4068)
thank you | 2020-09-13T10:49:32 | 2020-09-13T10:49:32 | {} | NONE |
vuejs | core | 688,311,341 | 2,064 | posva | Ah, nice catch. Didn't notice they were using different Vue versions. Sorry for the noise @znck 😓 | 2020-09-07T13:02:35 | 2020-09-07T13:02:35 | {} | MEMBER |
vuejs | core | 688,386,087 | 2,064 | skyweaver213 | Thank you for your help. It was a mistake I wasn't aware of. 😓
@skirtles-code @HcySunYang @znck @posva
| 2020-09-07T15:14:12 | 2020-09-07T15:14:12 | {} | NONE |
vuejs | core | 689,927,668 | 2,054 | yyx990803 | in v3, `v-for` is compiled as a single fragment node. You will need to check the fragment's children for the list items. | 2020-09-10T02:04:16 | 2020-09-10T02:04:16 | {
"-1": 3
} | MEMBER |
vuejs | core | 689,996,991 | 2,086 | HcySunYang | This has already been fixed: https://github.com/vuejs/vue-next/commit/ac81dcf0cc7f5fc722a0c14d1cc92ece5cc0db07, please wait for the new release. | 2020-09-10T05:37:42 | 2020-09-10T05:37:42 | {
"eyes": 1
} | MEMBER |
vuejs | core | 690,335,824 | 2,072 | edison1105 | make sense. | 2020-09-10T14:42:18 | 2020-09-10T14:42:18 | {} | MEMBER |
vuejs | core | 691,194,512 | 2,078 | CyberAP | The only line I changed was this:
```html
<component :is="Component" ref="custom" />
```
To this:
```html
<component :is="Component" :ref="custom" />
```
Do note that `console.log(value.$el)` takes a lot of time in JSFiddle because it prints that object in its own console. If you just log `1` it will wo... | 2020-09-11T16:30:02 | 2020-09-11T16:30:20 | {} | CONTRIBUTOR |
vuejs | core | 691,310,941 | 2,100 | yyx990803 | 1. Proxies will always have different identity from its target. The best practice is to never keep a reference of the raw object and only work with the reactive version of it.
2. https://v3.vuejs.org/api/basic-reactivity.html#markraw | 2020-09-11T21:03:34 | 2020-09-11T21:03:34 | {} | MEMBER |
vuejs | core | 687,755,677 | 2,058 | Fuzzyma | > You should ensure that the component is always registered correctly, why do you need unregistered components?
Yeah, of course. Still it shouldn't error out, right? :)
Especially since there is a warning that the component is unknown and therefore some would think that it is handled gracefully.
Great that you f... | 2020-09-06T10:54:14 | 2020-09-06T10:54:14 | {} | NONE |
vuejs | core | 687,758,642 | 2,056 | HcySunYang | Just added here for the record: the optimization mode doesn't have a mechanism to reuse DOM, and the `patchBlockChildren` is just a one-to-one diff, we cannot guarantee that the VNodes in dynamicChildren are at the same level, so there is no way to achieve key-based reuse.
I thought of a solution: due to a Fragment wi... | 2020-09-06T11:08:37 | 2020-09-06T11:08:37 | {} | MEMBER |
vuejs | core | 688,497,654 | 2,018 | bzd2000 | @yyx990803 , For me it is a bug. The doc clearly explains that props are One-Way Data Flow
_All props form a one-way-down binding between the child property and the parent one: when the parent property updates, it will flow down to the child, but not the other way around. **This prevents child components from acci... | 2020-09-07T20:16:50 | 2020-09-07T20:34:56 | {} | NONE |
vuejs | core | 689,469,099 | 2,076 | ZhangJian-3ti | This implement seems introduce worse performance than current one, also may cause more usage of memory since the ref flag attached to every single instance instead only exists in prototype. | 2020-09-09T10:18:01 | 2020-09-09T10:18:01 | {} | CONTRIBUTOR |
vuejs | core | 690,039,486 | 2,081 | HcySunYang | I cannot reproduce the issue according to your steps, maybe you need to provide more detailed info, such as device information, what browser... | 2020-09-10T07:13:24 | 2020-09-10T07:13:24 | {} | MEMBER |
vuejs | core | 690,040,146 | 2,087 | xxholly32 | o lifecycle-hooks changed ,i got it ,ty | 2020-09-10T07:14:42 | 2020-09-10T07:14:42 | {} | NONE |
vuejs | core | 690,045,685 | 2,081 | posva | This is because you are using a keyboard that works similar to IME https://v3.vuejs.org/guide/forms.html#basic-usage (see the note about Chinese)
My guess is you are using a Google keyboard that has some autocompletion. `v-model` intentionally delay setting the variable if the event is composing (https://developer.m... | 2020-09-10T07:25:19 | 2020-09-10T07:25:19 | {} | MEMBER |
vuejs | core | 690,935,414 | 2,097 | 07akioni | > This is one way to implement the same features in vue3. No need to use a new app.
> ~Sorry for using jsx~
>
> use it
What's more, when using sfc the usage is too complicate for a component library user.
despite of message-privider, new usage
```
export default {
setup () {
return {
message: i... | 2020-09-11T07:48:05 | 2020-09-11T07:48:40 | {} | CONTRIBUTOR |
vuejs | core | 687,926,557 | 549 | BinarySpike | Reading some guides online that have `createComponent` and I got
```
Module '"../../../node_modules/vue/dist/vue"' has no exported member 'createComponent'. Did you mean 'ConcreteComponent'?ts(2724)
```
Saw the merge and thought, "I wonder if it's renamed" and yes it is. 👍
The correct import is
```
import {... | 2020-09-06T23:01:15 | 2020-09-06T23:01:15 | {} | NONE |
vuejs | core | 688,165,783 | 2,064 | znck | As per spec component name should start with an upper case character. Compiler is treating helloworld as custom element. | 2020-09-07T08:38:26 | 2020-09-07T08:39:17 | {} | MEMBER |
vuejs | core | 689,073,956 | 2,071 | skirtles-code | It looks like a problem with `from` being missing:
https://github.com/vuejs/vue-next/blob/b53d45de65239fa4acd9c6bc41ed58fc9b823729/packages/runtime-core/src/componentOptions.ts#L461
I suspect that should be defaulting to `key` if `from` isn't set. | 2020-09-08T18:59:57 | 2020-09-08T18:59:57 | {} | CONTRIBUTOR |
vuejs | core | 689,431,383 | 2,044 | wong-lucy | > Use Vuex or a shared reactive object with provide/inject. Don't reach for parent like that.
thanks！！！I solved the problem。 | 2020-09-09T09:03:18 | 2020-09-09T09:03:18 | {} | NONE |
vuejs | core | 690,046,569 | 2,080 | posva | @lanezhao that rule is no longer true | 2020-09-10T07:26:54 | 2020-09-10T07:27:04 | {} | MEMBER |
vuejs | core | 690,963,689 | 2,097 | posva | If you want your library to render elements, give the user a component to put in their app where you pass the messages. The solution with a hoc by @lawvs also works
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2020-09-11T08:49:36 | 2020-09-11T08:49:36 | {} | MEMBER |
vuejs | core | 690,536,514 | 2,095 | KaelWD | Duplicate of #2054 | 2020-09-10T17:26:34 | 2020-09-10T17:26:34 | {} | CONTRIBUTOR |
vuejs | core | 690,074,456 | 2,085 | skirtles-code | It seems the template compiler is generating `{ key: itemKey(item) }` rather than `{ key: _ctx.itemKey(item) }`. That works in function mode but not in module mode. | 2020-09-10T08:19:17 | 2020-09-10T08:24:16 | {} | CONTRIBUTOR |
vuejs | core | 691,501,403 | 2,064 | lukef | Is there a solution that doesn't require roll-up? | 2020-09-12T14:49:45 | 2020-09-12T14:49:45 | {} | NONE |
vuejs | core | 690,081,130 | 2,081 | vallemar | My phone is a Huawei P30 PRO (Android 10) (EMUI 10.1.0).
My browser is google chrome, updated in the play store.
My keyboard is in Spanish and it's Google's. I have checked in the documentation for Vue 2 and the error is also present.
@posva My keyboard is very common, it is used by all Android, why is this not s... | 2020-09-10T08:31:37 | 2020-09-10T08:31:37 | {} | NONE |
vuejs | core | 690,872,625 | 2,097 | 07akioni | > Maybe you should use [resolveComponent](https://v3.vuejs.org/api/global-api.html#resolvecomponent) ~or [Teleport](https://v3.vuejs.org/guide/teleport.html#teleport)~?
>
> ```ts
> import { resolveComponent } from 'vue'
>
> this.$Message.info(() => h(resolveComponent('component-registered-on-app'), ...))
> ```
... | 2020-09-11T04:53:59 | 2020-09-11T04:55:54 | {} | CONTRIBUTOR |
vuejs | core | 691,198,469 | 2,099 | CyberAP | > <Suspense> now expects a single root node (cannot be fragment) for the default/fallback slots.
Can it be used with components wrapped with renderless components?
```html
<!-- Renderless.vue -->
<template>
<slot />
</template>
```
```html
<Suspense>
<Renderless>
<div />
</Renderless>
</Sus... | 2020-09-11T16:39:00 | 2020-09-11T16:39:00 | {} | CONTRIBUTOR |
vuejs | core | 691,627,761 | 2,105 | luthfimasruri | Ok, that absolutely makes sense @stefnotch, Thanks!!!! 👍 | 2020-09-13T07:35:22 | 2020-09-13T07:35:22 | {} | NONE |
vuejs | core | 688,170,819 | 2,064 | posva | What do you mean? the component is named `HelloWorld` and used as `<HelloWorld/>` | 2020-09-07T08:46:40 | 2020-09-07T08:46:40 | {} | MEMBER |
vuejs | core | 688,193,851 | 2,064 | znck | @posva Somehow `currentRenderingInstance` is missing and `resolveComponent` depends on it. RPV is working fine. Did we make any changes to `currentRenderingInstance`?
<img width="1792" alt="image" src="https://user-images.githubusercontent.com/2596484/92371539-5a51ad00-f119-11ea-9a43-3cc937839676.png">
| 2020-09-07T09:22:32 | 2020-09-07T09:22:32 | {} | MEMBER |
vuejs | core | 688,268,617 | 1,782 | underfin | @posva this is already fixed. | 2020-09-07T11:37:35 | 2020-09-07T11:37:35 | {
"heart": 1
} | MEMBER |
vuejs | core | 688,508,207 | 2,018 | yyx990803 | @bzd2000 note your issue is different from the original one. It's how Vue reactivity has always worked. If you want to explicitly prevent the child from mutating the state you passed down you can use `readonly`: https://v3.vuejs.org/api/basic-reactivity.html#readonly
But again, your use case sounds like wrong design... | 2020-09-07T20:54:46 | 2020-09-07T20:57:32 | {} | MEMBER |
vuejs | core | 690,895,509 | 2,097 | 07akioni | > This is one way to implement the same features in vue3. No need to use a new app.
> ~Sorry for using jsx~
>
> ```tsx
> // Message HOC
> import { Teleport, defineComponent, provide, ref } from 'vue'
>
> const Message = ({ open, text }) => (
> <Teleport to="body">{open && <div className="modal">{text}</div>... | 2020-09-11T06:04:51 | 2020-09-11T07:19:43 | {} | CONTRIBUTOR |
vuejs | core | 690,978,719 | 2,076 | basvanmeurs | Subclassing definately has a significant performance penalty.. I think it's better to keep it as it is. | 2020-09-11T09:21:01 | 2020-09-11T09:21:01 | {} | CONTRIBUTOR |
vuejs | core | 691,624,051 | 2,105 | stefnotch | I'll repeat it one more time
While this is initially a number and Typescript correctly identifies it as such.
`const num1 = ref(2);`
However, do not confuse it with actual strict typing like in other languages. The following still works and will assign a string to a number.
`num1.value = "hello world" as any"` ... | 2020-09-13T07:05:07 | 2020-09-13T07:05:50 | {} | NONE |
vuejs | core | 688,092,464 | 2,063 | jacekkarczmarczyk | https://github.com/vuejs/vue/issues/2308
Use `<dx-list></dx-list>` | 2020-09-07T07:16:34 | 2020-09-07T07:16:34 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 688,097,771 | 2,062 | posva | Or do not declare `tl` in `data` so it's not reactive | 2020-09-07T07:23:59 | 2020-09-07T07:23:59 | {} | MEMBER |
vuejs | core | 688,296,352 | 2,064 | skirtles-code | For what it's worth, I saw that same error message in a Webpack project. In that project the problem seemed to be that 2 copies of Vue were being pulled in. `resolveAsset` in a pre-built component was hitting a different Vue from the surrounding application, so it had a different `currentRenderingInstance`.
From a q... | 2020-09-07T12:35:21 | 2020-09-07T12:35:21 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 690,101,911 | 2,090 | posva | Always provide a repro when reporting a bug and please, write the issue in English so more people can help | 2020-09-10T09:11:11 | 2020-09-10T09:11:28 | {} | MEMBER |
vuejs | core | 689,997,566 | 2,085 | lanezhao | Disallow key attribute on `<template>`
https://eslint.vuejs.org/rules/no-template-key.html | 2020-09-10T05:39:08 | 2020-09-10T09:19:10 | {} | NONE |
vuejs | core | 691,045,981 | 2,097 | skirtles-code | I think this deserves further consideration.
The suggestion in the documentation to 'create a factory function' to share application configuration is much less straightforward than it sounds.
I've seen people ask about this several times on the forum and Stack Overflow, so it seems to be a common problem, and so ... | 2020-09-11T11:46:07 | 2020-09-11T11:46:07 | {
"+1": 12
} | CONTRIBUTOR |
vuejs | core | 691,623,489 | 2,105 | luthfimasruri | Yeah, I know that, I use `<script lang="ts">`
```
<script lang="ts">
...
</script>
```
| 2020-09-13T06:57:22 | 2020-09-13T06:57:22 | {} | NONE |
vuejs | core | 688,214,551 | 2,066 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/2054 | 2020-09-07T09:57:10 | 2020-09-07T09:57:10 | {} | MEMBER |
vuejs | core | 689,524,778 | 2,077 | AgileInteractive | If include/exclude could match some unique feature of the instance (type or the instance itself), it might be sufficient, but I am not sure if that is a better solution than just explicitly remove an instance of a vue component from the cache.
| 2020-09-09T12:19:03 | 2020-09-09T12:19:03 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.