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 | 618,776,399 | 1,040 | yyx990803 | As the readme says: please read the [RFCs](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0020-events-api-change.md) before opening issues. | 2020-04-24T03:06:35 | 2020-04-24T03:06:35 | {
"heart": 1
} | MEMBER |
vuejs | core | 619,039,643 | 1,043 | yyx990803 | 额外感谢翻译,现在 Composition API 官方页面有一个中文翻译的 PR - 建议可以参与审阅,两边可以比较一下,完善和统一一些术语、概念的译法:https://github.com/vuejs/composition-api-rfc/pull/23 | 2020-04-24T14:20:26 | 2020-04-24T14:20:26 | {} | MEMBER |
vuejs | core | 619,425,654 | 1,048 | ycmjason | closing for https://github.com/vuejs/vue-next/issues/1049 | 2020-04-25T18:59:11 | 2020-04-25T18:59:11 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 619,433,286 | 1,050 | michaeltintiuc | Closing due to the miracle of `rm -rf node_modules package-lock.json`, sorry for wasting anyone's time, looks like a version mismatch :feelsgood: | 2020-04-25T20:02:58 | 2020-04-25T20:02:58 | {
"-1": 5,
"heart": 1
} | NONE |
vuejs | core | 619,933,518 | 1,063 | mathe42 | You have to call `const p = toRefs(props).previewNote` or `const {previewNote} = toRefs(props)` to use the prop in watch. | 2020-04-27T11:50:45 | 2020-04-27T11:50:45 | {
"+1": 6
} | CONTRIBUTOR |
vuejs | core | 620,136,715 | 1,066 | pikax | @Tan90Qian you can only test lifecycle hooks in a element, you cannot use that hook outside of component.
Have a look at [vuejs/vue-test-util-next](https://github.com/vuejs/vue-test-utils-next)
And you can see how the lifecyle hooks are tested: https://github.com/vuejs/vue-test-utils-next/blob/master/tests/lifecyc... | 2020-04-27T17:51:10 | 2020-04-27T17:51:10 | {} | MEMBER |
vuejs | core | 620,319,736 | 1,066 | Tan90Qian | if I want to develop a `public` hook for a special scene without template or other view,I can not define it in a particular component.In this case, you mean that I can just use `watchEffect` or `watch` to implement responsive feature? @pikax
tips: the `mounted` and `unmounted` lifecycle is running correctly, the pr... | 2020-04-28T01:16:53 | 2020-04-28T01:32:41 | {} | NONE |
vuejs | core | 620,753,723 | 1,073 | shadowc | But it looks like it doesn't work when I use `modelValue` instead of `value`. What am I doing wrong? | 2020-04-28T17:39:44 | 2020-04-28T17:39:44 | {} | NONE |
vuejs | core | 621,237,105 | 1,080 | posva | What @thecrypticace said! | 2020-04-29T14:12:13 | 2020-04-29T14:12:13 | {} | MEMBER |
vuejs | core | 619,519,748 | 1,051 | pikax | @jonaskuske you right, this is actually a bug I spotted when trying to reproduce this issue.
I wasn't thinking straight last night, I will update the PR to reflect the bug I found, thank you. | 2020-04-26T09:47:31 | 2020-04-26T09:47:31 | {} | MEMBER |
vuejs | core | 621,025,144 | 1,075 | johnsoncodehk | I should use compiler (), not baseCompiler (). | 2020-04-29T07:01:10 | 2020-04-29T07:01:10 | {} | MEMBER |
vuejs | core | 618,972,124 | 1,042 | posva | That version of Vuex is for Vue 2, use `vuex@next` for Vue 3 | 2020-04-24T12:10:37 | 2020-04-24T12:10:37 | {} | MEMBER |
vuejs | core | 619,047,350 | 1,036 | yyx990803 | This is because when you use `this` inside class field initializers, it will point to the raw, unobserved version of the class instance. This is a caveat which unfortunately we have no way to detect, because the initialization happens before the class instance is even passed to `reactive`.
I assume you are doing thi... | 2020-04-24T14:32:40 | 2020-04-24T14:32:40 | {} | MEMBER |
vuejs | core | 619,309,605 | 1,042 | ChangedenCZD | > That version of Vuex is for Vue 2, use `vuex@next` for Vue 3
I just import vuex@4.0.0-alpha.1 | 2020-04-25T02:56:34 | 2020-04-25T02:56:34 | {
"+1": 1
} | NONE |
vuejs | core | 619,418,071 | 1,048 | pikax | no problems passing the stream
https://codesandbox.io/s/confident-smoke-bvwxf | 2020-04-25T18:00:48 | 2020-04-25T18:00:48 | {} | MEMBER |
vuejs | core | 619,425,340 | 1,048 | ycmjason | nice one thanks @jonaskuske | 2020-04-25T18:56:18 | 2020-04-25T18:56:18 | {} | CONTRIBUTOR |
vuejs | core | 620,751,666 | 1,073 | shadowc | Thanks for that info @mathe42 ! There's still an issue when wiring up the `@input` of the child component to a method that accepts that input, but that might be another issue altogether! | 2020-04-28T17:35:52 | 2020-04-28T17:35:52 | {} | NONE |
vuejs | core | 619,463,719 | 1,051 | jonaskuske | I don't think that wrapping this in a try/catch is enough to solve this. :/
As we're still casting to `""` instead of actually setting the property to `null` when it is required, in the following example stopping the video won't work since the browser will just ignore our attempt to set `srcObject` to `""` and keep pl... | 2020-04-26T01:19:54 | 2020-04-26T01:46:24 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 619,565,716 | 1,056 | yyx990803 | There is no `root` property on `SetupContext`. This is by design.
Code samples you see elsewhere may be outdated, refer to https://composition-api.vuejs.org/api.html for latest. | 2020-04-26T14:59:14 | 2020-04-26T14:59:53 | {
"+1": 1
} | MEMBER |
vuejs | core | 619,982,701 | 1,064 | mathe42 | The Problem is that msg is not a required Prop so it can happen that it doesn't exist on props. So after you do `let { msg } = toRefs(Props);` msg is `undefined` or a Ref.
So you have 2 Options:
1. Make Prop required:
```ts
props: {
msg: {
type: Object,
required: true
}
},
```
2. Te... | 2020-04-27T13:22:39 | 2020-04-27T13:22:39 | {} | CONTRIBUTOR |
vuejs | core | 622,065,624 | 1,047 | yyx990803 | And sorry for not noticing the tests, I thought it was a one line change without looking at it 🤦 | 2020-04-30T19:42:35 | 2020-04-30T19:42:35 | {} | MEMBER |
vuejs | core | 622,310,238 | 1,095 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test-dts](https://circleci.com/gh/vuejs/vue-next/4652?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 ... | 2020-05-01T09:03:30 | 2020-05-01T09:03:30 | {} | CONTRIBUTOR |
vuejs | core | 619,416,790 | 1,048 | jonaskuske | Hmm, it works for me.
Is your template coming from HTML/DOM instead of some build step by any chance? In that case the HTML parser will lowercase `srcObject` without you knowing, because attribute names in HTML are always lowercase. You can use `:src-object.camel.prop="userMediaStream"` instead and Vue will properly... | 2020-04-25T17:51:23 | 2020-04-25T17:51:23 | {} | CONTRIBUTOR |
vuejs | core | 620,051,351 | 1,066 | yyx990803 | Runtime test is used only for Vue's own tests. It's not meant to be a public package. Just use the normal `vue` package for testing. | 2020-04-27T15:17:18 | 2020-04-27T15:17:18 | {} | MEMBER |
vuejs | core | 620,746,494 | 1,073 | mathe42 | This works as expected: https://github.com/vuejs/rfcs/blob/master/active-rfcs/0011-v-model-api-change.md - I think... | 2020-04-28T17:26:11 | 2020-04-28T17:26:11 | {} | CONTRIBUTOR |
vuejs | core | 621,673,956 | 626 | dolymood | @pikax Thanks for your first review. I've merged vue-next master codes and fixed `extends` can't be `Mixin` problem. Unit tests https://github.com/vuejs/vue-next/pull/626/files#diff-7075cde1ccaf65deaa20bcce5d00eed2R558 , https://github.com/vuejs/vue-next/pull/626/files#diff-3764072b8e3b52266b03966f08a8c2d9R480 | 2020-04-30T07:50:42 | 2020-04-30T07:50:42 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 621,719,494 | 1,080 | xland | Thanks @posva @thecrypticace
Can I close that warning message?
I do not want to write `Suspense` tag in my parent template,
And I do not want to abstract my `await` code from the `async setup` function.
You know something like `await Promise.resolve(true);` will be excuted immediately.
Write `Suspense` tag... | 2020-04-30T09:24:54 | 2020-04-30T13:26:43 | {} | NONE |
vuejs | core | 622,040,167 | 1,047 | pikax | What do you think about the tests, do you think I'd worth having them? | 2020-04-30T18:57:27 | 2020-04-30T18:57:27 | {} | MEMBER |
vuejs | core | 622,310,656 | 1,096 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test-dts](https://circleci.com/gh/vuejs/vue-next/4655?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 ... | 2020-05-01T09:04:57 | 2020-05-01T09:04:57 | {} | CONTRIBUTOR |
vuejs | core | 622,391,717 | 1,096 | pikax | @dependabot rebase | 2020-05-01T13:37:27 | 2020-05-01T13:37:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 618,065,301 | 1,033 | elevatebart | I could see this problem be solved temporarily by resynchronizing the types of react and vue.
I would see this alignment as a nightmare to maintain in the long term. | 2020-04-22T22:06:11 | 2020-04-22T22:06:11 | {} | CONTRIBUTOR |
vuejs | core | 618,068,487 | 1,033 | elevatebart | Agreed, and choose when to do this switch from React JSX to Vue JSX.
What do you suggest?
## a bit of context
Vue-styleguidist uses React to render a style guide for VueJs components. Most of the code is in react though. Vue only comes in play in the preview. The reason being, same as for storybook, that the o... | 2020-04-22T22:14:57 | 2020-04-22T22:14:57 | {} | CONTRIBUTOR |
vuejs | core | 618,069,017 | 1,033 | elevatebart | I could create a Pull Request to expose what I think could be useful. | 2020-04-22T22:16:16 | 2020-04-22T22:16:16 | {} | CONTRIBUTOR |
vuejs | core | 618,219,974 | 993 | pikax | From what I've learned, `defineComponent` return `ctor` is actually an hack to make `h` do some validations.
I've done also an **hack** to make `defineComponent` return an `Component` valid. After sleeping over my solution, still not happy with it, personally I think having `PublicAPIComponent` as the public type co... | 2020-04-23T07:03:32 | 2020-04-23T07:03:32 | {} | MEMBER |
vuejs | core | 619,413,929 | 1,048 | ycmjason | Ohh sweet. Never knew about `.prop` 🤯 | 2020-04-25T17:30:13 | 2020-04-25T17:30:13 | {} | CONTRIBUTOR |
vuejs | core | 619,418,236 | 1,048 | ycmjason | It failed when I try to set it to `null`. Perhaps that's a bug? If you can reproduce, I'll close those and file a new bug. | 2020-04-25T18:01:40 | 2020-04-25T18:01:40 | {} | CONTRIBUTOR |
vuejs | core | 621,213,390 | 1,080 | thecrypticace | As I understand it a component with async setup is meant to be a child of the suspense component so you'd have to do something like the the following:
```vue
<Suspense>
<template #default>
<MyComponentWithAsyncSetup>
</template>
<template #fallback>loading...</template>
</Suspense>
``` | 2020-04-29T13:38:35 | 2020-04-29T13:38:35 | {
"+1": 5
} | CONTRIBUTOR |
vuejs | core | 621,385,050 | 1,081 | aztalbot | Use `Object.assign` and make sure to have a new object reference rather than the initial state object itself.
```js
setup() {
const initialState = {
name: "",
lastName: "",
email: ""
};
const form = reactive({ ...initialState });
function resetForm() {
Object.as... | 2020-04-29T18:28:52 | 2020-04-29T18:28:52 | {
"+1": 21,
"eyes": 2,
"heart": 3
} | CONTRIBUTOR |
vuejs | core | 622,391,475 | 1,095 | pikax | @dependabot rebase | 2020-05-01T13:36:52 | 2020-05-01T13:36:52 | {
"+1": 1
} | MEMBER |
vuejs | core | 601,823,922 | 860 | yyx990803 | This is the result of Node.js only branches being dropped at build time. | 2020-03-20T17:30:50 | 2020-03-20T17:30:50 | {} | MEMBER |
vuejs | core | 609,499,874 | 925 | mathe42 | No Bug: https://github.com/vuejs/vue-next/commit/21bcdec9435700cac98868a36716b49a7766c48d
See also https://github.com/vuejs/rfcs/pull/154 | 2020-04-05T23:04:47 | 2020-04-05T23:05:46 | {} | CONTRIBUTOR |
vuejs | core | 611,418,948 | 945 | mika76 | Hey @yyx990803 - I see the changes and have played with them a bit in the template explorer - but it doesn't look like the ` ` issue is sorted - it's still getting converted to a normal space.
| 2020-04-09T09:04:36 | 2020-04-09T09:08:58 | {} | NONE |
vuejs | core | 602,691,994 | 873 | shshaw | Talked with @znck a little about this, here was the feedback:
> The issue is caused by line 13. You're using a non bundler build mostly.
>
> As the contents of withScopeId function are only included in bundler builds.
>
> ```
> export function withScopeId(id: string): <T extends Function>(fn: T) => T {
> ... | 2020-03-23T15:57:24 | 2020-03-23T15:57:24 | {} | NONE |
vuejs | core | 608,433,455 | 915 | yyx990803 | Nice job! | 2020-04-03T13:28:20 | 2020-04-03T13:28:20 | {} | MEMBER |
vuejs | core | 609,077,805 | 910 | jods4 | @yyx990803 I was working on other stuff and the bug went away with an unrelated change.
I have even less idea now what happened. It seems wrong that a null `selected` was accessed inside a slot that was under a `v-if=selected` but I can't reproduce it anymore.
Also can't exclude I was doing something stupid.
Sh... | 2020-04-04T19:27:55 | 2020-04-04T19:27:55 | {} | CONTRIBUTOR |
vuejs | core | 610,116,218 | 929 | yyx990803 | Closing since `attrs` inspection has been improved in ec4a4c1e0688bca05022f21a959750f848b7aed1
For Vuex specific problems please open issue in Vuex repo instead. | 2020-04-07T01:07:59 | 2020-04-07T01:07:59 | {} | MEMBER |
vuejs | core | 601,987,871 | 861 | CyberAP | Mixins are not deprecated and this is a breaking change for them. | 2020-03-21T03:37:38 | 2020-03-21T03:37:38 | {} | CONTRIBUTOR |
vuejs | core | 603,719,639 | 878 | posva | Given the differences between Vue and 2 and 3, it makes sense to have different plugin versions as well. Do you have any example of plugin that correctly supports both Vue 2 and 3 on the same version? | 2020-03-25T08:53:15 | 2020-03-25T08:53:15 | {} | MEMBER |
vuejs | core | 606,583,042 | 901 | danyadev | It's rather strange that it is necessary to use `ref` here, because `reactive` returns the same reactive object. Maybe this was done for definiteness, because the names are the same. But it seems to me that it is best to get refs from the setup arguments, as described in [this](https://github.com/vuejs/rfcs/issues/146)... | 2020-03-31T11:59:41 | 2020-03-31T11:59:41 | {} | CONTRIBUTOR |
vuejs | core | 606,730,207 | 902 | danyadev | Oh, thanks! About the fact that [[Target]] returns not its value, I also did not know :) | 2020-03-31T16:19:54 | 2020-03-31T16:19:54 | {} | CONTRIBUTOR |
vuejs | core | 611,517,012 | 945 | yyx990803 | @mika76 a non-breaking whitespace is visually indistinguishable from a normal whitespace in the source code, but they are in fact different characters. If you copy it and compare it to a normal space in your console you'll see. | 2020-04-09T13:06:23 | 2020-04-09T13:06:23 | {
"+1": 1,
"hooray": 1
} | MEMBER |
vuejs | core | 604,776,779 | 884 | leaves4j | got it. | 2020-03-27T02:05:02 | 2020-03-27T02:05:02 | {} | NONE |
vuejs | core | 606,710,878 | 902 | yyx990803 | The proxy target is the internal instance, but the proxy itself only exposes public instance properties.
I'd like to also point out that grabbing a child component reference and write code based on inspection result is generally a bad idea - it creates non-contracted coupling between the parent and the child. If the... | 2020-03-31T15:49:13 | 2020-03-31T15:49:13 | {} | MEMBER |
vuejs | core | 609,589,508 | 929 | ysj16 | appContext exist on context but not context.attrs | 2020-04-06T06:24:45 | 2020-04-06T06:28:13 | {} | CONTRIBUTOR |
vuejs | core | 609,627,699 | 929 | sonicoder86 | `context.appContext` is `undefined` also | 2020-04-06T07:38:09 | 2020-04-06T07:38:09 | {} | NONE |
vuejs | core | 602,229,544 | 847 | jiangying000 | @jods4
I think Vue could work nice with strict type check in user land eventually.
As an example, we can simply modify line 71 (or 66) and your posted case will pass the check<del> (while did't loss type safeness, I guess)</del>
https://github.com/vuejs/vue-next/blob/b3890a93e39342fd16e5fd72c59f361fc211309c/pa... | 2020-03-22T15:50:04 | 2020-03-22T17:17:35 | {
"hooray": 1
} | CONTRIBUTOR |
vuejs | core | 603,843,956 | 879 | yyx990803 | See https://github.com/vuejs/vue-next/issues/878#issuecomment-603843866 | 2020-03-25T13:37:44 | 2020-03-25T13:37:44 | {} | MEMBER |
vuejs | core | 606,652,009 | 902 | underfin | The template should be `<Foo ref="foo" />`, not `<Foo ref="roo" />` | 2020-03-31T14:10:11 | 2020-03-31T14:10:11 | {} | MEMBER |
vuejs | core | 606,668,124 | 902 | yyx990803 | The `ref` exposes a public instance (equivalent to `this` in options API), there is no `vnode` property on a public component instance. | 2020-03-31T14:37:25 | 2020-03-31T14:37:25 | {} | MEMBER |
vuejs | core | 606,717,575 | 902 | danyadev | In my application, I want to get scrollTop and scrollHeight from a component that creates custom scrollbars, whose first child is "viewport". I need these values to preserve the scroll position when adding new elements.
But I still did not understand how I can get an HTML element from a component... | 2020-03-31T15:56:53 | 2020-03-31T15:56:53 | {} | CONTRIBUTOR |
vuejs | core | 609,063,121 | 910 | jods4 | @yyx990803 The simple repro is fixed but I'm still having issues in my project.
Not sure what I can do because it's a lot more complex than a simple repro.
That said, this fragment:
```html
<ui-form
v-if="selected != null"
@save="updateGroup(selected)"
>
<!-- ... more stuff inside -->
... | 2020-04-04T17:34:51 | 2020-04-04T17:34:51 | {} | CONTRIBUTOR |
vuejs | core | 609,393,548 | 923 | jods4 | @yyx990803 what's the recommended way to write a renderer that creates a `v-model`? | 2020-04-05T10:24:21 | 2020-04-05T10:24:21 | {} | CONTRIBUTOR |
vuejs | core | 601,988,362 | 861 | rigor789 | Right, i mixed it up! :+1: | 2020-03-21T03:42:20 | 2020-03-21T03:42:20 | {} | CONTRIBUTOR |
vuejs | core | 602,143,090 | 847 | jiangying000 | This is cause by tsconfig `strict` switch automatically turns on `strictFunctionTypes`, which makes function type parameter positions being checked contravariantly instead of bivariantly.
details: [#18654](https://github.com/Microsoft/TypeScript/pull/18654)
set `strictFunctionTypes: false` can be used as a tempor... | 2020-03-22T03:39:56 | 2020-03-22T12:09:01 | {} | CONTRIBUTOR |
vuejs | core | 602,773,119 | 874 | yyx990803 | Not really. At this stage WebAssembly based solutions leads to questionable performance gain (wasm can't directly touch the DOM), large binary size (which actually reduces load performance), difficulty of debugging during development (can't just read the stack trace and the source code), significantly larger surface of... | 2020-03-23T18:19:32 | 2020-03-23T18:20:18 | {
"+1": 2
} | MEMBER |
vuejs | core | 603,717,214 | 878 | CyberAP | > `version` is already exported by `vue`:
>
> ```js
> import { version } from 'vue'
> ```
For Vue 2.x and 3.x compatible plugins that would mean importing the whole Vue package. | 2020-03-25T08:48:16 | 2020-03-25T08:48:16 | {} | CONTRIBUTOR |
vuejs | core | 604,529,309 | 886 | yyx990803 | Closing but open to a PR to warn this case. | 2020-03-26T16:26:04 | 2020-03-26T16:26:04 | {} | MEMBER |
vuejs | core | 608,057,350 | 910 | jods4 | Using a component here is the key difference. If you do `<div v-if='some'>` instead then everything works fine. | 2020-04-02T19:24:43 | 2020-04-02T19:24:43 | {} | CONTRIBUTOR |
vuejs | core | 609,500,283 | 925 | sionzee | So solution is to define props twice now?
One as interface for typescript and second one for Vue? | 2020-04-05T23:08:06 | 2020-04-05T23:08:06 | {} | NONE |
vuejs | core | 609,817,369 | 929 | yyx990803 | 1. `attrs` is all fallthrough attributes and it has nothing to do with `appContext`. The reason you see `appContext` in the console is because `attrs` is a proxy pointing to the internal instance. This is a side effect of using Proxies and I'm working on improving this so it shows actual attrs in the console.
2. To ... | 2020-04-06T14:07:37 | 2020-04-06T14:07:37 | {
"+1": 1
} | MEMBER |
vuejs | core | 612,050,497 | 677 | yyx990803 | This is fixed in a6e2b105 | 2020-04-10T14:22:27 | 2020-04-10T14:22:27 | {
"rocket": 2
} | MEMBER |
vuejs | core | 603,862,177 | 878 | CyberAP | @yyx990803, what I meant by that is that you can't do this if the target version is Vue 2, since Vue 2 does not provide such an export. That would be useful for a cross-version compatible plugin that works on both Vue 2 and Vue 3. But I guess checking `'version' in Vue` would do the trick. | 2020-03-25T14:12:54 | 2020-03-25T14:12:54 | {} | CONTRIBUTOR |
vuejs | core | 609,079,328 | 402 | panstromek | I just stumbled upon this thread randomly and I need to say that I would stay away from microoptimizations like this because they have very noisy and unpredictable results. Since this is not the first time I see things like this here, I have a few things to note:
1. Browsers have multiple ways to run the same cod... | 2020-04-04T19:41:10 | 2020-04-08T19:41:18 | {
"+1": 4,
"heart": 7,
"rocket": 2
} | NONE |
vuejs | core | 602,975,786 | 575 | chjtx | @JasKang Come on!! | 2020-03-24T02:37:09 | 2020-03-24T02:37:09 | {} | NONE |
vuejs | core | 604,454,097 | 887 | yyx990803 | If anything, the RFC is still open: https://github.com/vuejs/rfcs/pull/148 | 2020-03-26T14:13:05 | 2020-03-26T14:13:05 | {} | MEMBER |
vuejs | core | 606,654,030 | 902 | danyadev | Wow, really. Now I get Proxy, but still can not get a single value:

| 2020-03-31T14:13:36 | 2020-03-31T14:13:36 | {} | CONTRIBUTOR |
vuejs | core | 606,659,432 | 902 | danyadev | I still can't get `vnode` | 2020-03-31T14:22:31 | 2020-03-31T14:22:31 | {} | CONTRIBUTOR |
vuejs | core | 609,010,176 | 918 | danyadev | I found another typo

| 2020-04-04T10:45:31 | 2020-04-04T10:45:31 | {} | CONTRIBUTOR |
vuejs | core | 609,067,270 | 910 | yyx990803 | Well... can't really tell anything without a repro. If you can maybe extract part of your project into something runnable, I can take a look. | 2020-04-04T18:04:58 | 2020-04-04T18:04:58 | {} | MEMBER |
vuejs | core | 609,109,272 | 923 | yyx990803 | Yeah, this does expose a problem that can happen even in compiled usage. Although I still strongly suggest **not** relying on any of the internals / undocumented exports. They may break without notice in any release. | 2020-04-05T00:29:32 | 2020-04-05T00:29:32 | {} | MEMBER |
vuejs | core | 609,877,669 | 934 | yyx990803 | There is already a warning for such cases. | 2020-04-06T15:50:42 | 2020-04-06T15:50:42 | {} | MEMBER |
vuejs | core | 603,330,953 | 861 | yyx990803 | Closed via 528621b
Note the behavior is different from Vue 2:
- merge strategies no longer apply to built-in options.
- the default value is now an empty object and no longer exposes merge strategies for built-in options.
There will be an RFC for the behavior change. | 2020-03-24T16:03:28 | 2020-03-24T16:03:50 | {
"+1": 1
} | MEMBER |
vuejs | core | 609,061,603 | 919 | Gkxie | > Why would you even add both the original and the observed version of the same object as keys in the same map?
>
> The basic rule of thumb when using v3's reactivity system is if you intend to make something reactive, create the reactive version directly and work only with the reactive version. Forget about the ori... | 2020-04-04T17:23:43 | 2020-04-04T17:23:43 | {} | NONE |
vuejs | core | 609,099,547 | 923 | jods4 | Believe it or not, it came naturally while building a reusable component that wraps an `<input>`.
I believe it doesn't have to be that convoluted, though.
### Problem 1, cached assign
For the cached `assign` problem, I'd like to ask you a question:
Are you supposed to be able to build a `v-model` from a render fu... | 2020-04-04T22:48:53 | 2020-04-04T22:48:53 | {} | CONTRIBUTOR |
vuejs | core | 609,501,485 | 925 | mathe42 | Just add
`props: {test: String}`
to your options.
Types are automatic. | 2020-04-05T23:17:12 | 2020-04-05T23:17:12 | {} | CONTRIBUTOR |
vuejs | core | 609,722,860 | 929 | sonicoder86 | The reason behind this is to reach the `store` instance and use it in the setup method. Map functions of the store are working but I can't combine them with the `setup` method as they reside on the `this` scope. | 2020-04-06T10:54:24 | 2020-04-06T10:54:24 | {} | NONE |
vuejs | core | 609,931,720 | 929 | sonicoder86 | Thanks, it works like a charm.
What is the desired way when dealing with the store in the new API?
If I have a component only with mappers and don't need anything else, should I move them to the `setup` function or just leave it there?
Here is the component with only mappers:
https://github.com/blacksonic/todom... | 2020-04-06T17:29:55 | 2020-04-06T17:29:55 | {} | NONE |
vuejs | core | 610,181,326 | 936 | 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-07T05:25:57 | 2020-04-07T05:25:57 | {} | CONTRIBUTOR |
vuejs | core | 603,433,607 | 876 | rigor789 | That sure sounds like the way to go!
So with `hasUnknownElements` set to `true` the following templates would produce the same render function:
```html
<StackLayout>
<Label/>
</StackLayout>
<!-- would be the same as -->
<component is="StackLayout">
<component is="Label" />
</component>
```
Is that co... | 2020-03-24T18:33:40 | 2020-03-24T18:33:40 | {} | CONTRIBUTOR |
vuejs | core | 603,843,866 | 878 | yyx990803 | Note in 3.0 the first argument received by plugins is no longer the same global `Vue` as in 2.x. It's a 3.0 app instance instead. The app instance only exposes global configuration related APIs as specified in https://github.com/vuejs/rfcs/blob/master/active-rfcs/0009-global-api-change.md - you won't be able to use oth... | 2020-03-25T13:37:34 | 2020-03-25T13:40:06 | {
"-1": 1
} | MEMBER |
vuejs | core | 603,847,796 | 777 | yyx990803 | Landed in alpha.10 via c3bb316 | 2020-03-25T13:45:16 | 2020-03-25T13:45:16 | {
"hooray": 2,
"rocket": 1
} | MEMBER |
vuejs | core | 604,433,341 | 884 | yyx990803 | They are not missing. This is a monorepo using yarn workspaces and these dependencies are specified in sub-packages. The root `package.json` only contains workspace level dependencies. | 2020-03-26T13:32:53 | 2020-03-26T13:32:53 | {} | MEMBER |
vuejs | core | 608,271,741 | 912 | cexbrayat | @yyx990803 There is also a leftover `debugger` instruction in `startMeasure`: is it on purpose or should it be removed? | 2020-04-03T07:16:18 | 2020-04-03T07:16:18 | {} | MEMBER |
vuejs | core | 609,003,559 | 919 | LinusBorg | We only track the raw key here (line 30):
https://github.com/vuejs/vue-next/blob/7402951d945b4e49474661594992a95f878de3f0/packages/reactivity/src/collectionHandlers.ts#L23-L37
and then in the `deleteEntry` handler, we check first forthe key as-is (which means here: being a proxy), and if that's not found, a possi... | 2020-04-04T09:39:43 | 2020-04-04T10:02:53 | {} | MEMBER |
vuejs | core | 609,059,200 | 920 | yyx990803 | Thanks, see https://github.com/vuejs/vue-next/commit/5dcc645fc068f9a467fa31ba2d3c2a59e68a9fd7 | 2020-04-04T17:06:48 | 2020-04-04T17:06:48 | {} | MEMBER |
vuejs | core | 609,670,320 | 929 | posva | I think that's private API: https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/component.ts#L102 and that's why it's hidden | 2020-04-06T09:07:09 | 2020-04-06T09:07:09 | {} | MEMBER |
vuejs | core | 601,793,970 | 858 | mannok | Does it mean that we cannot get the value before mutation if we use `@vue/reactivity` instead of `vue` as `watch` is only available in vue component? If I did not misunderstand, only watch support previous value. | 2020-03-20T16:32:28 | 2020-03-20T16:32:28 | {} | NONE |
vuejs | core | 602,171,436 | 847 | jods4 | @djy0 thanks for digging the root cause amongst TS options.
Do you think this is something that Vue could fix in its definitions, or is `strictFunctionTypes` never gonna play nice with this? | 2020-03-22T09:38:49 | 2020-03-22T09:38:49 | {} | CONTRIBUTOR |
vuejs | core | 603,055,775 | 874 | ZhangJian-3ti | Got it, thanks for your detailed explanation. | 2020-03-24T06:48:15 | 2020-03-24T06:48:15 | {} | CONTRIBUTOR |
vuejs | core | 603,364,719 | 876 | yyx990803 | I think f529dbd happens to address the issues you have here:
- Native element calls were made to work with compiled slots (auto calls `default()` slot and use as children)
- `resolveDynamicComponent` falls back to native strings if component is not found
We can simply replace `resolveComponent` with `resolveDynami... | 2020-03-24T16:53:24 | 2020-03-24T16:53:24 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.