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 | 678,321,700 | 1,916 | yyx990803 | Does this happen only on iOS 12.0 or all 12.x? Can someone try it on 12.1?
If it's 12.0 only I'm afraid this is going to be a wontfix since it's technically a bug in the JavaScript Core bundled with iOS 12 and according to [stats](https://www.statista.com/statistics/1118925/mobile-apple-ios-version-share-worldwide/#... | 2020-08-21T14:32:07 | 2020-08-21T14:32:25 | {} | MEMBER |
vuejs | core | 678,645,678 | 1,932 | pikax | > But `gen` is called, so `val.value` should be accessed? Or does `computed` not invoke inner functions to track dependencies?
The `gen(val)` will only execute when you iterate (ie: after setup), meaning that the access is not inside of the computed method and not tracked by it. | 2020-08-22T14:09:28 | 2020-08-22T14:09:28 | {} | MEMBER |
vuejs | core | 678,649,847 | 1,932 | pikax | because the computed `cached` the first `gen()`, and because your `watch` is only looking for `val` changes it always executes it. | 2020-08-22T14:47:32 | 2020-08-22T14:47:32 | {} | MEMBER |
vuejs | core | 677,798,709 | 1,886 | skirtles-code | @yyx990803 In Vue 2, accessing `this` allowed access to injections, properties from `Vue.prototype` and the store. Any one of these could have been used to provide a default based on configuration/locale/theme.
In particular, the documentation includes the following example for `provide`/`inject`:
```js
const Ch... | 2020-08-20T17:28:53 | 2020-08-20T17:28:53 | {} | CONTRIBUTOR |
vuejs | core | 678,623,820 | 1,932 | posva | Your computed property has no dependencies because it's not reading the value from `val`, so it never changes. Access `val.value` to track it:
```js
const iter = computed(() => {
val.value
return gen(val)
})
``` | 2020-08-22T10:29:07 | 2020-08-22T10:29:33 | {} | MEMBER |
vuejs | core | 678,722,785 | 1,935 | unbyte | when value updated, `v-model` will set `input.value` to the new value no matter whether the `input.value` is equal to the new value or not.
accoring to https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#setting-minimum-input-length-requirements:-the-minlength-attribute , **the value validated by... | 2020-08-23T03:05:31 | 2020-08-23T03:31:00 | {} | CONTRIBUTOR |
vuejs | core | 678,754,125 | 1,935 | Zohenn | @unbyte The PR you provided will probably fix that, however, just like you see, the problem still persists when ditching `v-model` in favor of `:value` and `@input`. This also doesn't seem to be an issue with Vue 2.
Not quite sure what the correct solution should be. I can probably use `pattern` instead of `minlengt... | 2020-08-23T09:58:07 | 2020-08-23T10:18:07 | {} | NONE |
vuejs | core | 674,952,943 | 1,847 | pikax | You can use `defineComponent`
```ts
export const MyComponent = defineComponent( (
props,
{ emit, slots }
) => {
emit("foo", "bar");
return h("div", props, slots);
})
``` | 2020-08-17T15:35:42 | 2020-08-17T15:35:42 | {
"+1": 1
} | MEMBER |
vuejs | core | 675,135,676 | 1,870 | abdullahseba | Yarn works because it copies the local package over which is hopeless for plugin development. `yarn link "plugin"` creates a symlink but then the same issue occurs. Vue is resolved in the linked repo but in my case, Webpack tries to resolve vue in the same directory as the template is located in which fails unless ... | 2020-08-17T21:58:00 | 2020-08-17T21:58:00 | {} | NONE |
vuejs | core | 677,414,788 | 1,734 | haoqunjiang | ```vue
<template v-for="item in list" :key="item.id1">
<MyButton :foo="item">One</MyButton>
<MyButton :foo="item">Two</MyButton>
</template>
```
is compiled as the equivalent of
```vue
<template v-for="item in list">
<Fragment :key="item.id1">
<MyButton :foo="item">One</MyButton>
... | 2020-08-20T07:24:21 | 2020-08-20T07:24:21 | {} | MEMBER |
vuejs | core | 677,411,856 | 1,894 | Picknight | Yeap, you are right. @yyx990803
I have an additional question: **Is it impossible to know whether an object is reactive from type inference?**
```js
const mRef = ref([{ k: "foo" }]);
const test = mRef.value[0];
console.log(isReactive(test)); // true
```
`test` is a plain reactive object which has reactive p... | 2020-08-20T07:22:35 | 2020-08-20T07:27:10 | {} | CONTRIBUTOR |
vuejs | core | 677,716,660 | 1,884 | yyx990803 | Great job! | 2020-08-20T14:56:40 | 2020-08-20T14:56:40 | {} | MEMBER |
vuejs | core | 678,250,724 | 1,916 | posva | It looks like iOS 12 still traverses the property `__v_reactive` even though it is not enumerable and it wouldn't show up on the final `JSON.stringify` result.
You can create a copy of the value as a workaround:
```js
JSON.stringify({ ...s })
```
That way the non-enumerable keys will be dropped as they shoul... | 2020-08-21T11:49:16 | 2020-08-21T11:49:16 | {} | MEMBER |
vuejs | core | 678,311,970 | 1,926 | posva | Please check the error in the console, you need to put `my-component` inside the `template`:
```vue
<my-component>
<template v-slot:default>
<my-component></my-component>
</template>
</my-component>
``` | 2020-08-21T14:12:57 | 2020-08-21T14:12:57 | {} | MEMBER |
vuejs | core | 678,578,678 | 1,917 | yyx990803 | I found a way to directly support `htm.bind(h)` without breaking Vue's idiomatic `h` usage in 54d06ec4.
Also, a few notes:
1. There is no need for `defineComponent` if you are *not* using TS
2. you can return the render function from `setup()`
So your code can be further simplified to:
```js
const html = ht... | 2020-08-22T01:59:22 | 2020-08-22T01:59:39 | {
"+1": 1
} | MEMBER |
vuejs | core | 678,646,036 | 1,932 | SebastianSpeitel | But why did it retrigger the render then? | 2020-08-22T14:13:15 | 2020-08-22T14:13:15 | {} | NONE |
vuejs | core | 676,224,132 | 1,891 | posva | @HcySunYang I also thought this was fixed by your PR but it seems to fail: https://github.com/vuejs/vue-next/compare/master...test/types/props-default | 2020-08-19T11:55:15 | 2020-08-19T11:55:15 | {} | MEMBER |
vuejs | core | 676,650,911 | 1,880 | yyx990803 | `defineComponent` returns a constructor type so it works with TSX.
I've widened `Component` to include the constructor type in eb2ae44d - this would make `Component` equivalent to previous `PublicAPIComponent` and the previous `Component` was renamed to `ConcreteComponent`. | 2020-08-19T20:21:16 | 2020-08-19T20:21:16 | {} | MEMBER |
vuejs | core | 676,732,575 | 1,890 | sionzee | In my case I have fixed sidebar on the page what have `overflow-y` set to scroll. The sidebar contains elements which could be dragged outside sidebar, these elements are in relative mode to parent. When the elements are being dragged outside of sidebar they are switched to absolute mode but the elements are cropped be... | 2020-08-19T21:47:57 | 2020-08-19T21:59:12 | {} | NONE |
vuejs | core | 677,436,021 | 1,734 | ota-meshi | I get it! Thank you! | 2020-08-20T07:50:47 | 2020-08-20T07:50:47 | {} | MEMBER |
vuejs | core | 678,321,966 | 1,927 | dream2023 | By the way, it works in template。 | 2020-08-21T14:32:38 | 2020-08-21T14:32:38 | {} | CONTRIBUTOR |
vuejs | core | 678,333,017 | 1,925 | yyx990803 | Our impression is that there are still many big organizations with slow moving IT infrastructure updates that are stuck with IE11 (mostly internal systems), and there are a fair share of users who still need to support it.
That said, Microsoft coming up with explicit timelines for IE11 deprecation could be a good si... | 2020-08-21T14:54:14 | 2020-08-21T14:54:14 | {
"+1": 27,
"eyes": 4
} | MEMBER |
vuejs | core | 678,674,128 | 1,934 | posva | `setup` only runs once when the component is instantiated. To display a loader when you fetch data because of a changing data or prop, you need to handle the state yourself.
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2020-08-22T18:16:38 | 2020-08-22T18:16:38 | {} | MEMBER |
vuejs | core | 677,402,595 | 1,734 | haoqunjiang | I think that should be considered as a bug. | 2020-08-20T07:16:55 | 2020-08-20T07:16:55 | {} | MEMBER |
vuejs | core | 677,758,778 | 1,906 | ivanheral | Hi @yyx990803,
accepts more than 3 arguments when add Fragment.
I have an example using vue3 with htm with the problem. | 2020-08-20T16:10:27 | 2020-08-20T16:10:44 | {} | NONE |
vuejs | core | 678,249,273 | 1,919 | underfin | I don't think this is a better way, it is a break change which use `renderSlot(slot, 'default')` instead of `slot.default()`. Maybe we should revert change with https://github.com/vuejs/vue-next/commit/791eff3dfbd6be9ba8d597ecf8d943cd197f9807. I think it is better if disable track dynamicChildren with computed visiting... | 2020-08-21T11:45:11 | 2020-08-21T11:45:11 | {} | MEMBER |
vuejs | core | 678,412,196 | 1,900 | yyx990803 | Great job! Wondering if vnode creation would benefit from this - let's find out? :) | 2020-08-21T17:49:17 | 2020-08-21T17:49:17 | {} | MEMBER |
vuejs | core | 678,414,999 | 1,917 | yyx990803 | I'm sorry but this is not a fix. Vue's `h` function has its own signature and it doesn't try to be compatible with JSX implementations that expect children to be arg-based. **This is by design**.
If you want to use Vue's `h` with `htm` you can create a wrapper function that passes its rest arguments as an array to V... | 2020-08-21T17:55:54 | 2020-08-21T17:58:25 | {
"+1": 1
} | MEMBER |
vuejs | core | 678,623,331 | 1,931 | posva | Marked as a bug because it works on Vue 2 | 2020-08-22T10:22:57 | 2020-08-22T10:22:57 | {} | MEMBER |
vuejs | core | 678,675,155 | 1,934 | bhaidar | Sure @posva I will check the forums and Discord chat.
Just to close this thread, Suspense is not applicable in this scenario? | 2020-08-22T18:25:50 | 2020-08-22T18:25:50 | {} | NONE |
vuejs | core | 678,677,310 | 1,934 | posva | No | 2020-08-22T18:47:03 | 2020-08-22T18:47:03 | {
"+1": 1
} | MEMBER |
vuejs | core | 678,746,508 | 1,936 | HcySunYang | Is it this one: https://github.com/vuejs/vue-next/pull/1883? I just noticed it, I will close this PR. | 2020-08-23T08:37:05 | 2020-08-23T08:37:05 | {} | MEMBER |
vuejs | core | 675,296,855 | 1,847 | michaeltintiuc | I think the `defineComponent` declaration should also be patched as it has `... & FunctionalComponent<Props>` resulting in the same error. Although I can do `FunctionalComponent<Props, string[] | {}>` to mitigate it, yet it does not render the component properly unless I `return () => h('div', props, slots);` | 2020-08-18T07:04:25 | 2020-08-18T07:18:48 | {} | NONE |
vuejs | core | 677,670,303 | 1,906 | yyx990803 | This is the wrong fix. `h` only accepts 3 arguments. JSX implementations should generate code using `createVNode`. | 2020-08-20T13:38:47 | 2020-08-20T13:38:47 | {} | MEMBER |
vuejs | core | 677,744,443 | 1,912 | yyx990803 | Good catch - however I noticed the logic can actually be simplified, see 91700fbe | 2020-08-20T15:44:14 | 2020-08-20T15:44:14 | {} | MEMBER |
vuejs | core | 678,320,911 | 1,927 | dream2023 | 
| 2020-08-21T14:30:31 | 2020-08-21T14:30:31 | {} | CONTRIBUTOR |
vuejs | core | 678,369,143 | 1,928 | posva | See the note at https://vuejs.org/v2/api/#vm-watch, this is expected when mutating objects. Will pass on the information about the note missing in v3.
| 2020-08-21T16:06:02 | 2020-08-21T16:06:02 | {
"+1": 1
} | MEMBER |
vuejs | core | 678,644,833 | 1,932 | posva | gen creates the generator but doesn't read the cal.value | 2020-08-22T14:01:30 | 2020-08-22T14:01:30 | {} | MEMBER |
vuejs | core | 678,645,580 | 1,934 | posva | `Suspense` works by waiting the promise returned inside `setup`, so you will need to add an `await fetchData()` inside of it. Something like this:
```js
let promise
watchEffect(async () => {
promise = new Promise(resolve => {
if (props.country) {
setTimeout(async () => {
... | 2020-08-22T14:08:34 | 2020-08-22T14:09:16 | {} | MEMBER |
vuejs | core | 671,292,636 | 1,822 | posva | Open a new issue once you have a boiled down reproduction | 2020-08-10T11:07:26 | 2020-08-10T11:07:26 | {} | MEMBER |
vuejs | core | 671,792,134 | 1,826 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/1409 | 2020-08-11T07:57:55 | 2020-08-11T07:57:55 | {} | MEMBER |
vuejs | core | 674,087,359 | 1,850 | yyx990803 | Oh that's true, yeah `transition` does require its inner component to have single roots. We should probably have a better warning for this case. | 2020-08-14T13:56:23 | 2020-08-14T13:56:23 | {} | MEMBER |
vuejs | core | 674,893,914 | 1,870 | yyx990803 | I tested your repro and noticed that it works fine using Yarn, but not with NPM. This is likely due to different ways the package managers handle `file:` dependencies.
With npm's linking, the bundler (in this case `webpack`) will try to resolve `vue` from the file that is being processed, so it will use the version ... | 2020-08-17T13:50:17 | 2020-08-17T13:50:17 | {
"+1": 1
} | MEMBER |
vuejs | core | 674,928,828 | 1,869 | BillSchumacher | Wait what? It doesn't work... you want me to document.select instead of using a ref? Kinda defeats the purpose. | 2020-08-17T14:52:17 | 2020-08-17T14:52:17 | {} | NONE |
vuejs | core | 672,922,192 | 1,835 | zhangzhonghe | After my test, this did not fix #1789. | 2020-08-12T14:55:01 | 2020-08-12T14:55:01 | {} | MEMBER |
vuejs | core | 673,459,986 | 1,845 | 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/8036?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-08-13T12:52:36 | 2020-08-13T12:52:36 | {} | CONTRIBUTOR |
vuejs | core | 673,539,960 | 1,848 | michaeltintiuc | Closing due to github creating 2 issues | 2020-08-13T15:18:01 | 2020-08-13T15:18:01 | {} | NONE |
vuejs | core | 673,863,432 | 1,816 | Picknight | > Talking about the readability, I think the current one is better. It's clearer to have the logic in an if branch, focus on what we should deal with. With an extra return, it does reduce the indent but definitely increase the cost of reading the code, you have to keep reminding yourself it's actually introduced an els... | 2020-08-14T03:30:24 | 2020-08-14T03:30:24 | {} | CONTRIBUTOR |
vuejs | core | 674,432,877 | 1,865 | posva | It doesn't show any error after upgrading vue dependencies to the latest ones. On your repro I removed the yarn.lock file and ran yarn and everything works | 2020-08-15T18:28:52 | 2020-08-15T18:28:52 | {} | MEMBER |
vuejs | core | 674,434,352 | 1,865 | danyadev | Did you switch from branch `master` to `bug-2` exactly? The `master` branch also has a button, so you could confuse them. | 2020-08-15T18:43:53 | 2020-08-15T18:43:53 | {} | CONTRIBUTOR |
vuejs | core | 674,923,587 | 1,869 | posva | Using the Composition API, you should be able to get reactive refs though. But passing around the elements like that looks like a bad design unless you are integrating a vanilla JS library with Vue | 2020-08-17T14:43:20 | 2020-08-17T14:43:20 | {} | MEMBER |
vuejs | core | 671,811,809 | 1,825 | pearofducks | @posva - Yeah, same intention - that `modelModifiers` is a recognized "prop" for a native `input` instead of being treated as an unknown HTML attribute - and that any built-in modifiers are used. Sorry if my example wasn't clear!
Again, I have absolutely no objection to this functionality being provided some other w... | 2020-08-11T08:36:02 | 2020-08-11T08:36:02 | {} | NONE |
vuejs | core | 673,650,705 | 1,816 | dsonet | Talking about the readability, I think the current one is better. It's clearer to have the logic in an if branch, focus on what we should deal with. With an extra return, it does reduce the indent but definitely increase the cost of reading the code, you have to keep reminding yourself it's actually introduced an else ... | 2020-08-13T18:52:29 | 2020-08-13T18:52:29 | {} | CONTRIBUTOR |
vuejs | core | 673,740,170 | 1,850 | yyx990803 | Possible duplicate of #1782 | 2020-08-13T22:24:35 | 2020-08-13T22:24:35 | {} | MEMBER |
vuejs | core | 673,870,633 | 1,850 | dani17r | @yyx990803 If it helps, I found that the problem is not with the transitions or the `<router-view>` tags. The problem really is in the `<template>` when I use multiple roots (fragments). And when I wrap my components in a `<div>` everything works fine, that is, there are problems to support fragments in components when... | 2020-08-14T04:02:47 | 2020-08-14T10:55:25 | {} | NONE |
vuejs | core | 674,435,537 | 1,865 | danyadev | I deleted all yarn cache, `node_modules` and `yarn.lock` and tried to install dependencies absolutely from scratch - it doesn't matter, the error is still reproducible.
| 2020-08-15T18:56:39 | 2020-08-15T18:56:39 | {} | CONTRIBUTOR |
vuejs | core | 674,925,052 | 1,877 | soultice | > The library [hooper](https://github.com/baianat/hooper) is built for vue2 **not** vue3.
As stated in my comment above, I trying to migrate Hooper from vue2 to vue3.
> When opening a bug report please provide a boiled down reproduction without external libraries as the bug could come from the library itself. Als... | 2020-08-17T14:45:51 | 2020-08-17T14:45:51 | {} | NONE |
vuejs | core | 674,282,300 | 1,843 | yyx990803 | It is necessary for this test case: 223f1805 | 2020-08-14T21:36:10 | 2020-08-14T21:36:10 | {
"+1": 1
} | MEMBER |
vuejs | core | 674,434,170 | 1,865 | danyadev | I just removed `node_modules` and `yarn.lock`, typed in `yarn` and started the application again - the error is reproducible as well.
Also on my main project, I updated all dependencies in the same way and the problem **did not** get resolved. | 2020-08-15T18:42:22 | 2020-08-15T18:42:36 | {} | CONTRIBUTOR |
vuejs | core | 671,793,064 | 1,827 | posva | This is related to how TS works, the `as const` is necessary in this case because you took the props object outside of `defineComponent` | 2020-08-11T07:59:53 | 2020-08-11T07:59:53 | {} | MEMBER |
vuejs | core | 673,740,831 | 1,851 | 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-08-13T22:26:40 | 2020-08-13T22:26:40 | {} | CONTRIBUTOR |
vuejs | core | 673,906,471 | 1,811 | paulshen | Thanks for the reply @yyx990803! This makes sense
To avoid the case you describe, could the computed properties be marked dirty on dep set but updated on a tick, similar to reactive effects? Basically non-eager and async. If something reads before the delayed tick, it has the dirty flag. There is probably another tr... | 2020-08-14T06:12:48 | 2020-08-14T06:12:48 | {} | NONE |
vuejs | core | 673,958,387 | 1,679 | advdv | I'm unable to get this to work:
```js
console.log(Vue.version) //returns "3.0.0-rc.5"
var app = Vue.createApp({
data() {
return {counter: 0}
}
})
app.config.delimiters = ['{%', '%}']
app.mount("#app")
```
Am I doing anything wrong... | 2020-08-14T08:31:22 | 2020-08-14T08:31:35 | {} | NONE |
vuejs | core | 674,278,545 | 1,816 | yyx990803 | `== null` checks for both `null` and `undefined`. In this case it doesn't really make a difference. As for the early return - we generally don't encourage readability related PRs since they are subjective but usually ends up in messy diffs that makes the git history harder to follow. | 2020-08-14T21:25:02 | 2020-08-14T21:25:02 | {
"+1": 1
} | MEMBER |
vuejs | core | 674,619,360 | 1,869 | BillSchumacher | Refs from child objects are not passed back to parent and parent refs are not passed down to children, accessing refs after mounted and from methods also does not give the correct result. | 2020-08-17T02:08:53 | 2020-08-17T02:09:11 | {} | NONE |
vuejs | core | 674,720,112 | 1,811 | Picknight | 1. I run the example provided by @paulshen in master branch [619efd9](https://github.com/vuejs/vue-next/commit/619efd9ac5a0d38651b7282722e7b347a013411a), the trigger frequency of `watch` is the same as that of `onUpdated`:
```shell
App.vue?3dfd:22 computedCount updated 0
App.vue?3dfd:27 updated
App.vue?3dfd:22 comp... | 2020-08-17T07:46:26 | 2020-08-17T07:47:43 | {} | CONTRIBUTOR |
vuejs | core | 671,348,533 | 1,818 | posva | Can you provide a boiled down repro? | 2020-08-10T13:17:49 | 2020-08-10T13:17:49 | {} | MEMBER |
vuejs | core | 671,463,232 | 858 | ByScripts | I'm trying to build a lib for Vue 3 using `@vue/reactivity`. But I don't know how to get the `watch` behavior when updating an array.
If I have an array with 8 items, then _unshifting_ an item will execute the `effect` 9 times.
If I log the steps, the array looks like this:
```
- ['a', 'b', 'c', 'd', 'e', 'f'... | 2020-08-10T16:41:03 | 2020-08-10T16:41:03 | {} | NONE |
vuejs | core | 671,927,657 | 1,796 | dependabot-preview[bot] | Looks like @types/jest is up-to-date now, so this is no longer needed. | 2020-08-11T12:51:08 | 2020-08-11T12:51:08 | {} | CONTRIBUTOR |
vuejs | core | 671,960,113 | 1,825 | HcySunYang | This one won't work correctly:
> `<input v-model="model" v-bind="{ modelModifiers }">`
Maybe we need to support dynamic modifiers:
```html
<input v-model.[dynamicModifiers]="model">
```
The value of `dynamicModifiers` can be:
- `string`: `'foo'`
- `Array<string>`: `['foo']`
- `object`: `{ foo: true }`
So ... | 2020-08-11T13:52:31 | 2020-08-11T13:52:31 | {
"+1": 5
} | MEMBER |
vuejs | core | 673,077,496 | 1,804 | yyx990803 | Thanks for the PR, but it should be 0 indentation on lines > 1000 so `abs` is incorrect here. See #1807 | 2020-08-12T19:53:18 | 2020-08-12T19:53:36 | {
"+1": 1
} | MEMBER |
vuejs | core | 673,107,329 | 1,809 | yyx990803 | TS 4 doesn't contain significant breaking changes and does not affect how Vue is used with it, so Vue 3 will likely support both TS 3.9 and 4.x. Or, put it another way, there isn't a strong reason for us to **not** support TS 3.x for the time being, since it won't prevent you from using TS 4 with Vue 3.
This does br... | 2020-08-12T20:58:12 | 2020-08-12T20:58:28 | {
"heart": 2
} | MEMBER |
vuejs | core | 673,908,422 | 1,854 | HcySunYang | CI failure is not caused by this PR | 2020-08-14T06:18:55 | 2020-08-14T06:18:55 | {} | MEMBER |
vuejs | core | 674,344,820 | 1,862 | syuilo | See https://github.com/vuejs/rfcs/pull/97 | 2020-08-15T04:00:24 | 2020-08-15T04:00:24 | {} | CONTRIBUTOR |
vuejs | core | 674,397,505 | 1,864 | unbyte | @Picknight I think it's a better solution than #1799 | 2020-08-15T13:39:12 | 2020-08-15T13:39:28 | {} | CONTRIBUTOR |
vuejs | core | 674,493,938 | 1,846 | Picknight | See #1682 | 2020-08-16T07:51:23 | 2020-08-16T07:51:23 | {} | CONTRIBUTOR |
vuejs | core | 671,569,556 | 1,824 | posva | You need to use `inheritAttrs` https://v3.vuejs.org/api/options-misc.html#inheritattrs | 2020-08-10T20:19:46 | 2020-08-10T20:19:46 | {
"+1": 1
} | MEMBER |
vuejs | core | 673,074,619 | 1,840 | yyx990803 | You can avoid exposing raw refs to the template (i.e retain the old behavior) by wrapping your `element` property with `reactive`:
```diff
return {
- element
+ element: reactive(element)
}
```
It is technically possible to detect such cases in the compiler, but it is something better done at the tooling le... | 2020-08-12T19:47:16 | 2020-08-12T19:49:03 | {
"+1": 1
} | MEMBER |
vuejs | core | 674,078,185 | 1,857 | yyx990803 | `toRef` only works on a reactive object, you are calling it on a ref. Also the ref's initial value is `null` so you can't call `toRef` on its value anyway. You can probably use a `computed` though. | 2020-08-14T13:35:58 | 2020-08-14T13:36:13 | {} | MEMBER |
vuejs | core | 674,277,478 | 1,850 | dani17r | they should allow, what: `<ruter-view> <transition: name =" .. "> <keep-alive> <component: is =" ... "> <k ../> <t ../> < r ../> `can use the (fragments) in the components, it's more or less like there are no multiple roots in vue 3 when using components with <transition> inside <router-view> | 2020-08-14T21:21:56 | 2020-08-14T21:21:56 | {} | NONE |
vuejs | core | 674,334,258 | 1,859 | unbyte | > I don't think this is fixing the the issue linked. It is about properties added to an array, not refs inside arrays and empty string keys
`!targetIsArray || isSymbol(key) || isNaN(key as any) || key === ''` is it to judge whether the key is for an item or a property of the array. If it's a key for property, refs s... | 2020-08-15T02:14:42 | 2020-08-15T14:18:46 | {} | CONTRIBUTOR |
vuejs | core | 674,925,911 | 1,877 | pikax | > As stated in my comment above, I trying to migrate Hooper from vue2 to vue3.
Sorry my fault.
> I don't see how this counts as an external library
your dependency for `hooper` is pointing to your github repo, which is an external library. | 2020-08-17T14:47:24 | 2020-08-17T14:47:24 | {} | MEMBER |
vuejs | core | 673,308,391 | 1,836 | HcySunYang | I think we can simply remove the check for `shapeFlag`? | 2020-08-13T07:20:25 | 2020-08-13T07:20:25 | {} | MEMBER |
vuejs | core | 673,771,282 | 1,836 | zhangzhonghe | @HcySunYang I am not sure!🙂 | 2020-08-14T00:16:40 | 2020-08-14T00:16:40 | {} | MEMBER |
vuejs | core | 674,440,758 | 1,866 | sqal | `mixins` accepts an array of partial component's options so you should wrap your fn in the methods object in order to be correctly merged:
```js
export default {
methods: {
setup() { console.log(123); }
}
}
```
other alternatives:
// shared
```js
export const foo = () => {}
export const b... | 2020-08-15T19:51:22 | 2020-08-15T19:51:22 | {} | CONTRIBUTOR |
vuejs | core | 674,937,506 | 1,877 | posva | Then you should open the bug on the library's repo | 2020-08-17T15:07:24 | 2020-08-17T15:07:24 | {} | MEMBER |
vuejs | core | 674,940,341 | 1,877 | pikax | > Yes, and as I am trying to point out the bug occurs when providing a component as a library, so this will always be a bug in an external library, there is no way for me to prove it otherwise.
To vue they are objects, regardless if it comes from an external library or `JSON.parse(componentJSON)` or some other way t... | 2020-08-17T15:12:35 | 2020-08-17T15:12:35 | {} | MEMBER |
vuejs | core | 671,887,727 | 1,829 | posva | Tested using the fiddle with the latest Vue 3 at #1828 and it works. (Note you have to use `backgroundColor: 'blue'` instead of `background` | 2020-08-11T11:22:55 | 2020-08-11T11:22:55 | {} | MEMBER |
vuejs | core | 671,960,203 | 1,830 | posva | When reporting a bug please make sure the reproduction is runnable and boiled down (no Firebase).
The error suggests you have a cyclic reference in your object (the object references itself). Marking the data as raw with `markRaw` should also work but it won't be reactive. You can use a `shallowRef` to make it react... | 2020-08-11T13:52:41 | 2020-08-11T13:52:41 | {} | MEMBER |
vuejs | core | 673,862,434 | 1,853 | elevatebart | For reference here is the original issue.
https://github.com/vue-styleguidist/vue-styleguidist/issues/942 | 2020-08-14T03:26:08 | 2020-08-14T03:26:08 | {} | CONTRIBUTOR |
vuejs | core | 674,354,794 | 1,861 | posva | You need to use v-bind instead: `v-bind:d="pat"`
https://v3.vuejs.org | 2020-08-15T06:02:10 | 2020-08-15T06:02:28 | {} | MEMBER |
vuejs | core | 674,585,238 | 1,837 | nstuyvesant | Thanks @HcySunYang. I went a different route to solve the problem but it was with your suggestion to use render functions. Here's the now working FormGroup component code:
```typescript
import { defineComponent, h, ComponentOptions } from "vue"
import { FormInputContext } from "@/use/form-input-validation"
export... | 2020-08-16T22:22:11 | 2020-08-16T22:22:11 | {} | NONE |
vuejs | core | 673,230,546 | 1,837 | HcySunYang | What if we change our mental model? for your use case, I think it can be achieved simply by `provide/inject`.
This is the executable code:
```ts
import { h, createApp, defineComponent, provide, inject, InjectionKey } from 'vue'
const FormGroupContext: InjectionKey<{
register(validator: Function): void
}> ... | 2020-08-13T03:30:36 | 2020-08-13T05:36:55 | {} | MEMBER |
vuejs | core | 674,018,894 | 1,850 | posva | If you want to use a `transition` component, its content must have one single root to apply the classes | 2020-08-14T10:58:23 | 2020-08-14T10:58:23 | {} | MEMBER |
vuejs | core | 674,350,059 | 1,816 | Picknight | Thanks for your explanation @yyx990803 , I got it. | 2020-08-15T05:04:18 | 2020-08-15T05:05:20 | {} | CONTRIBUTOR |
vuejs | core | 674,475,223 | 1,864 | unbyte | using switch instead of map and object is based on this benchmark
https://jsben.ch/Pt9NS | 2020-08-16T03:53:45 | 2020-08-16T03:53:45 | {} | CONTRIBUTOR |
vuejs | core | 674,914,306 | 1,877 | posva | When opening a bug report please provide a boiled down reproduction without external libraries as the bug could come from the library itself. Also avoid all the unnecessary things like typescript.
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2020-08-17T14:27:04 | 2020-08-17T14:27:04 | {} | MEMBER |
vuejs | core | 674,922,706 | 1,877 | pikax | ~~The library [hooper](https://github.com/baianat/hooper) is built for vue2 **not** vue3.~~ | 2020-08-17T14:41:45 | 2020-08-17T14:45:54 | {} | MEMBER |
vuejs | core | 674,932,802 | 1,869 | yyx990803 | 1. Child component is mounted before the parent, so it's possible for the parent ref to be not set yet when the child is mounted (this is why the child's `mounted` hook throws error)
2. Because of (1), you need to check the presence of the parent ref first, e.g. with something like `parentRefs.logo && parentRefs.log... | 2020-08-17T14:59:15 | 2020-08-17T14:59:39 | {} | MEMBER |
vuejs | core | 671,254,289 | 1,797 | dependabot-preview[bot] | Superseded by #1820. | 2020-08-10T09:30:43 | 2020-08-10T09:30:43 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.