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 | 671,796,686 | 1,827 | Jokcy | @posva so this do releated to `PropsOptions extends Readonly<ComponentPropsOptions>` defination in `defineComponent` right？ we need to declare `Props` as `readonly` | 2020-08-11T08:07:28 | 2020-08-11T08:07:28 | {} | CONTRIBUTOR |
vuejs | core | 672,741,150 | 1,787 | gem007bd | @yyx990803 can you please release this change? | 2020-08-12T08:46:48 | 2020-08-13T15:39:30 | {
"+1": 1
} | NONE |
vuejs | core | 674,345,192 | 1,862 | axetroy | Thx for you reply @syuilo | 2020-08-15T04:04:09 | 2020-08-15T04:04:09 | {} | NONE |
vuejs | core | 674,346,721 | 1,221 | beetaa | ok, I got it, https://github.com/vuejs/vue-next/issues/1414#issuecomment-647284774 | 2020-08-15T04:22:25 | 2020-08-15T04:22:25 | {} | NONE |
vuejs | core | 674,360,887 | 1,861 | sunshoutian | thx a lot. @posva | 2020-08-15T07:13:43 | 2020-08-15T07:13:43 | {} | NONE |
vuejs | core | 674,404,011 | 1,864 | Picknight | > @Picknight I think it's a better solution than #1799
Yep, I think this one is better.
btw, this PR essentially replaces the type judgment basis from `target.constructor` to `toRawType(target)`, I'm not sure if there is a potential problem. | 2020-08-15T14:18:44 | 2020-08-15T14:19:49 | {} | CONTRIBUTOR |
vuejs | core | 674,934,270 | 1,877 | soultice | 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.
I'll try to reproduce it in a simple component and see if that helps. | 2020-08-17T15:01:54 | 2020-08-17T15:03:30 | {} | NONE |
vuejs | core | 671,171,039 | 1,809 | 3zzy | > This beta takes us on our first step into TypeScript 4.0, and while it brings a new major version, don’t fret – there are no substantially larger breaking changes than usual. Our philosophy in evolving TypeScript has always been to provide an upgrade path that minimizes disruptive breaking changes while still giving ... | 2020-08-10T05:40:56 | 2020-08-10T05:40:56 | {} | NONE |
vuejs | core | 671,892,933 | 1,829 | MissedWarrior | @posva thanks for clarifcation. The only thing that I didn't undestand is behaviour when another variable is in the template: why does color always stay red(I reproduced it in repo with 3.0.0-rc.5)? Does it trigger another update cycle that updates the state of styles? | 2020-08-11T11:35:07 | 2020-08-11T11:38:00 | {} | NONE |
vuejs | core | 672,979,702 | 1,835 | HcySunYang | Sure, and I updated this PR, now everything works correctly, the solution is:
- 1. unset ref synchronously (within the rendering cycle)
- 2. set ref in the "after rendering" queue
....CI failure does not seem to be related to this PR. | 2020-08-12T16:29:29 | 2020-08-12T16:29:29 | {} | MEMBER |
vuejs | core | 673,415,103 | 1,844 | posva | You have to call getCurrentInstance outside of the computed, same as provide and inject | 2020-08-13T11:10:50 | 2020-08-13T11:10:50 | {} | MEMBER |
vuejs | core | 674,078,649 | 1,853 | yyx990803 | Yeah, open to a PR | 2020-08-14T13:37:03 | 2020-08-14T13:37:03 | {} | MEMBER |
vuejs | core | 674,170,792 | 1,221 | beetaa | > When pre compiling templates, it needs to be configured at the compiler level.
@yyx990803 hi, how to achieve this (configured at the compiler level) while using vue3 and vite? Is that mean I should do it in `vite.config.js`? I encounter the same situation with this, have you solved the issue? @nshusr thank you. | 2020-08-14T17:03:06 | 2020-08-14T17:05:09 | {} | NONE |
vuejs | core | 674,435,874 | 1,865 | posva | I see it in the branch. The problem is you are using the same key for two different components because you are not filtering what you are keeping alive. So you have either provide a unique key based on the route path/name + the id, that way KeepAlive will be able to restore the correct component, or use
```vue
... | 2020-08-15T19:00:00 | 2020-08-15T19:00:00 | {
"+1": 6
} | MEMBER |
vuejs | core | 674,436,722 | 1,865 | danyadev | Oh, but I already had problems with the key for KeepAlive, and I met with them again.
Thanks, I used `route.name + id` for the key | 2020-08-15T19:08:26 | 2020-08-15T19:08:47 | {} | CONTRIBUTOR |
vuejs | core | 674,881,439 | 1,866 | yyx990803 | This is intentional. `mixins` is a part of the Options API and `setup` is part of the Composition API. If you are using the Composition API, all logic composition should be done using Composition API. | 2020-08-17T13:28:08 | 2020-08-17T13:28:08 | {
"+1": 9,
"confused": 19
} | MEMBER |
vuejs | core | 671,791,638 | 1,825 | posva | Do you mean being able to write
```vue
<input v-model="model" v-bind="{ modelModifiers }">
``` | 2020-08-11T07:56:55 | 2020-08-11T07:56:55 | {} | MEMBER |
vuejs | core | 671,922,988 | 1,831 | 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/7969?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-11T12:42:15 | 2020-08-11T12:42:15 | {} | CONTRIBUTOR |
vuejs | core | 672,884,252 | 1,800 | ais-one | I used
@material/mwc-select
@vaadin/vaadin-select
v-model does not do anything but :value and @change is good enough...
| 2020-08-12T13:52:47 | 2020-08-12T13:52:47 | {} | NONE |
vuejs | core | 673,862,236 | 1,853 | elevatebart | The condition would be replaced by
```js
} else if (!__DEV__ && node.type === NodeTypes.COMMENT && !comments) {
``` | 2020-08-14T03:25:19 | 2020-08-14T03:25:19 | {} | CONTRIBUTOR |
vuejs | core | 674,239,324 | 1,859 | posva | 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 | 2020-08-14T19:32:50 | 2020-08-14T19:32:50 | {} | MEMBER |
vuejs | core | 674,405,339 | 1,864 | unbyte | > Yep, I think this one is better.
>
> btw, this PR essentially replaces the type judgment basis from `target.constructor` to `toRawType(target)`, I'm not sure if there is a potential problem.
I've found this as a reference http://perfectionkills.com/instanceof-considered-harmful-or-how-to-write-a-robust-isarray/ | 2020-08-15T14:31:14 | 2020-08-15T14:31:14 | {} | CONTRIBUTOR |
vuejs | core | 674,430,529 | 1,866 | posva | I don't think there is a way but it wouldn't make sense because
instead you could create a function that returns
refs and methods and call it inside setup. This way you get typings and things are explicit.
For global mixins you can still use the options api | 2020-08-15T18:04:54 | 2020-08-15T18:04:54 | {
"+1": 1
} | MEMBER |
vuejs | core | 674,573,446 | 1,791 | CyberAP | I wonder if it makes sense to support this in a form of a built-in component instead of a component option?
It would then be possible to use promises to get a cache key:
```html
<template>
<server-cache :key="cacheKey">
<!-- rendered on cache miss, otherwise cached stringified component is used -->
<h... | 2020-08-16T20:24:24 | 2020-08-16T20:28:53 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 671,554,939 | 1,409 | AlexandreBonaventure | I ended up using this workaround:
```js
const vm = getCurrentInstance();
const router = vm?.ctx?.$router
if (router) ....
```
Although, ctx is marked as internal API... I wish there is a better way to solve this | 2020-08-10T19:52:30 | 2020-08-10T19:52:30 | {} | CONTRIBUTOR |
vuejs | core | 671,885,497 | 1,828 | posva | The vue version in codepen is really outdated. The version you provided seems to work well: https://jsfiddle.net/z5239asg/ But I found a different problem with https://jsfiddle.net/sy6qt3ce/ Removing the watcher shows a different behavior as well. I'm updating the issue to reflect the problem, which made me realize a s... | 2020-08-11T11:17:25 | 2020-08-11T11:17:25 | {} | MEMBER |
vuejs | core | 671,886,972 | 1,828 | posva | Ah, never mind, I found the original problem: https://github.com/vuejs/vue/issues/7756, it's a wont fix. Using `backgroundColor` in the provided jsfiddle works | 2020-08-11T11:21:00 | 2020-08-11T11:21:00 | {
"+1": 1
} | MEMBER |
vuejs | core | 672,905,740 | 1,798 | dependabot-preview[bot] | Superseded by #1839. | 2020-08-12T14:28:31 | 2020-08-12T14:28:31 | {} | CONTRIBUTOR |
vuejs | core | 673,019,627 | 1,840 | posva | Can you provide more context like about when this is biting you? | 2020-08-12T17:49:53 | 2020-08-12T17:49:53 | {} | MEMBER |
vuejs | core | 674,624,587 | 1,869 | BillSchumacher | Did some more testing, pretty convinced something is really wrong. In the console output, it shows a height of 200px everywhere when you expand the proxy target. However, no matter what I do it always returns 0 in the component. I'm fairly certain this was a thing in vue2. | 2020-08-17T02:34:06 | 2020-08-17T02:34:06 | {} | NONE |
vuejs | core | 671,992,471 | 1,813 | zhangzhonghe | I am trying to fix it. | 2020-08-11T14:49:05 | 2020-08-11T14:49:05 | {
"+1": 2
} | MEMBER |
vuejs | core | 673,739,560 | 1,811 | yyx990803 | This has to do with another optimization that prevents the computed getter from being over-eagerly evaluated too many times:
```js
const expensiveComputed = computed(() => {
return someArray.map(() => { ... })
})
for (let i = 0; i < 1000; i++) {
someArray.push({ ... })
}
```
If computed getters are e... | 2020-08-13T22:22:42 | 2020-08-13T22:22:42 | {
"eyes": 1
} | MEMBER |
vuejs | core | 674,393,749 | 1,843 | yangmingshan | Oh! That make sense. Thank you for the explanation. | 2020-08-15T12:59:42 | 2020-08-15T12:59:42 | {} | CONTRIBUTOR |
vuejs | core | 674,778,093 | 1,869 | Picknight | [Special Attributes - ref](https://v3.vuejs.org/api/special-attributes.html#ref)
> `$refs` is also non-reactive, therefore you should not attempt to use it in templates for data-binding | 2020-08-17T09:44:22 | 2020-08-17T09:44:22 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 671,053,027 | 1,815 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/1813 | 2020-08-09T13:36:01 | 2020-08-09T13:36:01 | {} | MEMBER |
vuejs | core | 671,314,035 | 1,809 | posva | Looking at the breaking change, it looks like there won't be anything blocking to support both TS 3 and 4. It needs to be tried for sure | 2020-08-10T12:01:45 | 2020-08-10T12:01:45 | {
"heart": 2
} | MEMBER |
vuejs | core | 671,350,879 | 1,817 | posva | You need to use unique keys for each toast (at https://github.com/ohepworthbell/vue3-dynamic-loop-bug/blob/props/src/App.vue#L17-L29 and anywhere they are created), otherwise they get reused by index in the array, reusing the state with the `transitioning` variable from the disappearing toast | 2020-08-10T13:22:16 | 2020-08-10T13:22:16 | {
"+1": 2
} | MEMBER |
vuejs | core | 671,360,563 | 1,818 | CyberAP | Turns out injection hook is called before provide, so it is not possible to self-inject. Sorry for the inconvenience. | 2020-08-10T13:40:23 | 2020-08-10T13:40:23 | {} | CONTRIBUTOR |
vuejs | core | 674,150,940 | 1,857 | beetaa | > `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.
@yyx990803 Thank you for pointing out the mistakes and providing the very helpful guidance, finally, I can get the co... | 2020-08-14T16:16:14 | 2020-08-14T16:16:14 | {} | NONE |
vuejs | core | 683,636,208 | 2,013 | posva | Not completely sure of the usage of slots like that but this also fails:
```js
setup(props, context){
return () => {
const defaults = context.slots.default()
const current = defaults.filter((tag) => {
return tag.props.title === props.selected
})[0]
console.log('ta... | 2020-08-31T08:15:17 | 2020-08-31T08:15:17 | {} | MEMBER |
vuejs | core | 683,662,749 | 2,015 | Fuzzyma | Interesting approach. But it becomes more complicated when you dont have access to the dom ref because the target is in some different component. How would you go about that? | 2020-08-31T09:10:38 | 2020-08-31T09:10:38 | {
"+1": 2
} | NONE |
vuejs | core | 684,003,330 | 2,019 | posva | IE 11 will be supported but it's not yet. What is the specific opera version you are targeting? | 2020-08-31T19:54:36 | 2020-08-31T19:54:36 | {} | MEMBER |
vuejs | core | 684,144,865 | 2,020 | Raiondesu | Still, for the exact use-case I provided, current types provide some weird results:
Props here are definitely required, but are still marked as optional in the type, with no obvious way around this, except f... | 2020-09-01T01:56:12 | 2020-09-01T01:57:00 | {} | NONE |
vuejs | core | 684,518,902 | 1,849 | ChesterBu | So,How to access the component Public instance in setup for now? | 2020-09-01T07:38:25 | 2020-09-01T07:38:25 | {} | CONTRIBUTOR |
vuejs | core | 686,580,783 | 2,004 | cathrinevaage | @yyx990803 The use case that prompted this was a that user wanted to, with the setup function, with valid typescript, compile and render a remotely fetched template, while injecting state into it.
```js
setup () {
const count = ref(1)
const template = '<button @click="count++">{{ count }}</button>'
retur... | 2020-09-03T15:44:26 | 2020-09-03T15:45:47 | {} | CONTRIBUTOR |
vuejs | core | 686,409,707 | 2,035 | luka-mikec | @yyx990803 The problem reappears when adding a new node with `v-else`, regardless of whether `v-once` is present in the new node. I updated my example: https://github.com/luka-mikec/vue-once-if-issue-demo/blob/master/src/App.vue
Edit: there is a problem with v-once inside v-for too, I added an example to the same fi... | 2020-09-03T10:53:02 | 2020-09-03T17:48:26 | {} | NONE |
vuejs | core | 683,553,620 | 2,015 | HcySunYang | I think the following approach should work correctly:
```js
createApp({
setup() {
const refDom = ref(null)
return () => [
// ref the DOM
h('div', { ref: refDom }),
h(Teleport, {
// set the target to refDom
to: refDom.value,
// disable teleport when refD... | 2020-08-31T05:14:23 | 2020-08-31T05:14:23 | {
"+1": 4
} | MEMBER |
vuejs | core | 684,512,813 | 2,020 | pikax | > Still, for the exact use-case I provided, current types provide some weird results:
> 
You need to cast `as const` because the required gets the type of `boolean` instead of `true`.
```ts
withProps(
... | 2020-09-01T07:26:50 | 2020-09-01T07:26:50 | {} | MEMBER |
vuejs | core | 684,803,283 | 2,018 | leopiccionia | Should a [`shallowRef`](https://v3.vuejs.org/api/refs-api.html#shallowref) suit your case?
From `ref` documentation:
> If an object is assigned as a ref's value, the object is made deeply reactive by the `reactive` method.
From `shallowRef` documentation:
> Creates a ref that tracks its own `.value` mutation bu... | 2020-09-01T12:05:12 | 2020-09-01T12:05:12 | {} | CONTRIBUTOR |
vuejs | core | 684,897,653 | 1,981 | Picknight | Can you provide a reproduction link? In this way, others can help you better 😁 | 2020-09-01T14:31:10 | 2020-09-01T14:31:10 | {} | CONTRIBUTOR |
vuejs | core | 684,986,859 | 1,987 | yyx990803 | Nice job tracking this down. I refactored it to avoid creating an extra function for every compiled slot. | 2020-09-01T16:38:26 | 2020-09-01T16:38:26 | {} | MEMBER |
vuejs | core | 685,704,993 | 2,027 | posva | Thanks! | 2020-09-02T12:36:06 | 2020-09-02T12:36:06 | {} | MEMBER |
vuejs | core | 685,731,479 | 2,036 | gregveres | ah, ok. I didn't know about that. Thanks.
Unfortunately, I am stuck on v2 using the composition api plugin until Vuetify ports to v3. I guess I will keep using the any cast or mock up an equivalent to useCssModule for my code so I am closer to being ready to port to v3 when Vuetify pulls the trigger. | 2020-09-02T13:19:34 | 2020-09-02T13:19:34 | {} | NONE |
vuejs | core | 685,248,687 | 1,981 | CarterLi | > I believe in Vue 3 prop declarations are optional.
1. For functional component: yes.
1. For normal component: no. | 2020-09-02T02:31:23 | 2020-09-02T02:31:23 | {} | CONTRIBUTOR |
vuejs | core | 685,737,597 | 2,036 | posva | Can you provide a boiled down reproduction? At this state, this isn't clear. Is it a Vue 2 or Vue 3 issue? | 2020-09-02T13:29:27 | 2020-09-02T13:29:45 | {} | MEMBER |
vuejs | core | 686,152,113 | 2,038 | zmtlwzy | thanks!!
onClickCapture
onClickOnce | 2020-09-03T00:10:45 | 2020-09-03T00:10:45 | {} | NONE |
vuejs | core | 684,078,260 | 1,982 | yyx990803 | When reviewing this I realized two things:
1. props/emits options need to be resolved per instance/component combo due to global mixins
2. the resolved options must be cached on the component using app instance uid as key, since the same component may get used in different apps with different global mixins!
3. We ... | 2020-08-31T22:35:12 | 2020-08-31T22:35:12 | {} | MEMBER |
vuejs | core | 685,215,244 | 2,004 | yyx990803 | This is somewhat intentional because the returned function is not intended to be user-callable. Its only use case is being passed as the `render` option to components. | 2020-09-02T00:58:08 | 2020-09-02T00:58:08 | {} | MEMBER |
vuejs | core | 685,246,268 | 2,011 | yyx990803 | I adjusted it to a simpler heuristics: if a v-model listener (onUpdate:xxx) has a corresponding declared prop, then it indicates the user expects to handle the `v-model` logic in this component so it listener should not fallthrough. | 2020-09-02T02:24:07 | 2020-09-02T02:24:07 | {} | MEMBER |
vuejs | core | 686,053,835 | 1,849 | yyx990803 | Ok, so the team actually is discussing an API to explicitly expose public methods, something like
```js
import { expose } from 'vue'
export default {
setup() {
expose({
reset() {
// ...
}
})
}
}
```
Either way I don't think it should be done by messing directly with th... | 2020-09-02T22:06:24 | 2020-09-02T22:06:24 | {
"hooray": 5
} | MEMBER |
vuejs | core | 686,445,288 | 1,886 | xxholly32 | Use inject to set props default value was possibile. did you have any solution now ? @skirtles-code | 2020-09-03T12:09:24 | 2020-09-03T12:09:24 | {} | NONE |
vuejs | core | 683,421,372 | 1,990 | designerzen | On further inspection feel free to keep this ticket closed.
The child component reference does actually resolve correctly with the latest RC and I have been unable to replicate the behavior I experienced in the async children - they all seem to be getting their refs at the expected onMount. 👍
I restarted Vite a... | 2020-08-30T13:33:36 | 2020-08-30T13:33:36 | {} | NONE |
vuejs | core | 684,808,417 | 2,025 | leopiccionia | For now, `RefImpl` is an implementation detail, and this implementation can change in future. In fact, refs weren't implemented as class instances until RC.7.
It seems like it's not being leaked to public API [intentionally](https://github.com/vuejs/vue-next/pull/1900#discussion_r474050847). | 2020-09-01T12:14:41 | 2020-09-01T12:14:41 | {} | CONTRIBUTOR |
vuejs | core | 685,232,152 | 1,849 | chenjiahan | This is our use case: expose some apis for component user
```js
// Form.jsx
export default {
name: 'MyForm',
setup() {
const vm = getCurrentInstance().proxy;
vm.reset = () => {
// reset form
};
return () => <div class="form"></div>
},
};
```
```html
<!-- App.vue -->
... | 2020-09-02T01:45:52 | 2020-09-02T01:45:52 | {} | CONTRIBUTOR |
vuejs | core | 685,742,948 | 2,036 | gregveres | @posva Sure..
```
export default defineComponent({
name: 'SCard',
setup(props) {
const { $style, $scopedSlots } = getCurrentInstance()!;
const sheetClasses = computed((): Dictionary<boolean> => {
const classes: Dictionary<boolean> = {};
classes[$style.heading] = true;
if (... | 2020-09-02T13:37:59 | 2020-09-02T13:37:59 | {} | NONE |
vuejs | core | 685,911,281 | 1,682 | rchl | My bad, will report there. | 2020-09-02T18:17:05 | 2020-09-02T18:17:05 | {} | NONE |
vuejs | core | 686,466,386 | 1,886 | skirtles-code | @xxholly32 Not directly. You could use a computed property to apply a default instead. | 2020-09-03T12:49:39 | 2020-09-03T12:49:39 | {} | CONTRIBUTOR |
vuejs | core | 686,566,469 | 2,042 | yyx990803 | `$` is a reserved prefix so you shouldn't be using it.
fa7ab0a now warns such cases and makes your case fail in both dev and prod. | 2020-09-03T15:22:10 | 2020-09-03T15:22:10 | {} | MEMBER |
vuejs | core | 686,870,658 | 2,043 | Picknight | The usage here is different from the [document](https://v3.vuejs.org/guide/composition-api-provide-inject.html#mutating-reactive-properties). 🧐
> However, there are times where we need to update the data inside of the component where the data is injected. In this scenario, we recommend providing a method that is re... | 2020-09-04T02:56:31 | 2020-09-04T02:56:31 | {} | CONTRIBUTOR |
vuejs | core | 686,887,615 | 2,043 | amrnn90 | @Picknight
providing a method that updates the ref and calling it in the child's setup makes no difference.
https://codesandbox.io/s/elated-meadow-6r04w?file=/src/Child.vue | 2020-09-04T03:54:03 | 2020-09-04T03:54:03 | {} | NONE |
vuejs | core | 687,629,948 | 2,054 | LemonAppleMo | In V2, children length is same
Link: https://codesandbox.io/s/serene-bouman-mwe4y?file=/src/App.vue | 2020-09-05T16:06:01 | 2020-09-05T16:08:47 | {} | NONE |
vuejs | core | 683,428,221 | 1,980 | FrankFang | https://github.com/vuejs/vue-next/issues/2013
No luck for 3.0.0-rc.6 | 2020-08-30T14:36:48 | 2020-08-30T14:51:02 | {} | NONE |
vuejs | core | 683,658,875 | 1,849 | HcySunYang | I still think we should revert it, it's especially useful in third-party libraries such as [vue-test-utils-next](https://github.com/vuejs/vue-test-utils-next), also very commonly used in component libraries. | 2020-08-31T09:02:41 | 2020-08-31T09:02:41 | {
"+1": 1
} | MEMBER |
vuejs | core | 684,671,932 | 2,020 | Raiondesu | Ok, thank you for a very detailed reply.
---
> Just to make it clear, "export all TS types" is not correct
I agree with this specific statement, which is why I've already corrected my point to "export all TS types used by public API" that better reflects my intentions and concerns.
---
> > But there are ... | 2020-09-01T09:39:46 | 2020-09-01T12:09:50 | {} | NONE |
vuejs | core | 685,899,257 | 1,682 | pikax | @rchl this is v3 repo and your issue is with the composition api plugin.
Vue2 reactivity system mutates the original object, so when you do reactive will change 6our state object and unwrap it, this as nothing to do with the template.
| 2020-09-02T17:54:16 | 2020-09-02T17:54:16 | {} | MEMBER |
vuejs | core | 687,330,976 | 2,045 | leopiccionia | The migration guide, as it currently stands, assume you're migrating from 2.6+ `vm.$scopedSlots` instead of the soft-deprecated 2.x `vm.$slots` (see [RFC](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0001-new-slot-syntax.md) and [announcement](https://medium.com/the-vue-point/vue-2-6-released-66aa6c8e785e)).
... | 2020-09-04T19:11:49 | 2020-09-04T19:11:49 | {} | CONTRIBUTOR |
vuejs | core | 687,721,054 | 2,057 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/1532 | 2020-09-06T08:05:30 | 2020-09-06T08:05:30 | {} | MEMBER |
vuejs | core | 684,084,762 | 2,018 | nerdcave | Would this be considered a "gotcha" to any degree or fully and predictably expected? I've chosen to use `toRef()` over `ref()` in these situations because it feels like it conveys the intent of the code much more accurately, but I'm not even sure if that's recommended. | 2020-08-31T22:55:24 | 2020-08-31T22:55:24 | {} | NONE |
vuejs | core | 684,835,901 | 2,026 | yyx990803 | It doesn't exist in Vue 3 because Vue 3 doesn't need it.
It will be provided in the IE11 build though. | 2020-09-01T13:02:36 | 2020-09-01T13:03:19 | {
"+1": 1
} | MEMBER |
vuejs | core | 685,197,497 | 2,026 | Fuzzyma | Doesn't that force us to write different code for the ie11 version and the other version? | 2020-09-02T00:06:04 | 2020-09-02T00:06:04 | {} | NONE |
vuejs | core | 685,247,838 | 2,027 | yyx990803 | `watch(route)` is implicitly `deep: true`, which traverses arbitrarily deep properties. So technically, this is expected behavior. Also, deep traversing a complex object when you only care about a few properties is wasteful.
Your use case can and **should** be rewritten using a computed property instead:
```js
c... | 2020-09-02T02:28:48 | 2020-09-02T02:29:39 | {
"+1": 30
} | MEMBER |
vuejs | core | 687,245,363 | 2,050 | Haroenv | thanks for fixing @yyx990803 :) | 2020-09-04T16:13:04 | 2020-09-04T16:13:04 | {} | NONE |
vuejs | core | 687,354,463 | 2,045 | Haroenv | Ah, that makes sense! I didn't migrate to the 2.6+ style in my project since I wanted to avoid breaking compatibility with older versions, but I guess it isn't the regular flow. Thanks for elaborating @leopiccionia | 2020-09-04T20:02:46 | 2020-09-04T20:02:46 | {} | NONE |
vuejs | core | 684,132,325 | 2,020 | Raiondesu | Ok, thank you very much for such a nice response.
But what about other use-cases I personally couldn't come up with? | 2020-09-01T01:13:45 | 2020-09-01T01:13:45 | {} | NONE |
vuejs | core | 684,835,614 | 2,025 | yyx990803 | This is intentional. The only reason class being used internally is performance. It's not meant to be extended. Use `customRef`. | 2020-09-01T13:02:08 | 2020-09-01T13:02:08 | {} | MEMBER |
vuejs | core | 685,783,306 | 2,037 | yyx990803 | When shorthand syntax is used on the component it is considered to be specifying the slot of that component.
Correct usage:
```html
<my-comp #test="slotProps">
<my-comp2>
<span class="green">{{ slotProps.item }}<span>
</my-comp2>
</my-comp>
```
Or, to be more explicit, use a `<template>`:... | 2020-09-02T14:43:01 | 2020-09-02T14:43:01 | {} | MEMBER |
vuejs | core | 683,823,518 | 2,018 | posva | This is probably because `items` is an array and passed by reference. Please don't provide read-only repros | 2020-08-31T14:43:14 | 2020-08-31T14:43:14 | {} | MEMBER |
vuejs | core | 683,830,087 | 2,013 | FrankFang | Isn't it a bug? | 2020-08-31T14:53:47 | 2020-08-31T14:53:47 | {} | NONE |
vuejs | core | 683,947,573 | 2,018 | nerdcave | @unbyte Understood, but should changes to the original still propagate all the way through? That seems unexpected. Added a simpler repo link that demonstrates. | 2020-08-31T18:21:16 | 2020-08-31T18:21:16 | {} | NONE |
vuejs | core | 687,183,401 | 2,043 | Picknight | The deep reason is [ac81dcf](https://github.com/vuejs/vue-next/commit/ac81dcf0cc7f5fc722a0c14d1cc92ece5cc0db07). @yyx990803 Maybe we should revert it ? | 2020-09-04T14:33:50 | 2020-09-04T14:33:50 | {} | CONTRIBUTOR |
vuejs | core | 687,625,746 | 2,054 | LemonAppleMo | > > These three forms are consistent
>
> Please be more precise, what do you exactly expect to be the same?
Slots length is not same. | 2020-09-05T15:28:24 | 2020-09-05T15:28:24 | {} | NONE |
vuejs | core | 687,721,112 | 2,057 | posva | @HcySunYang I think it's worth posting that comment on the other issue. It has useful information. | 2020-09-06T08:05:58 | 2020-09-06T08:05:58 | {} | MEMBER |
vuejs | core | 684,526,992 | 2,023 | posva | Thank you but this is intentional | 2020-09-01T07:53:04 | 2020-09-01T07:53:04 | {} | MEMBER |
vuejs | core | 685,320,529 | 2,027 | posva | Can you point me the part of the documentation so I can take a look? | 2020-09-02T06:00:53 | 2020-09-02T06:00:53 | {} | MEMBER |
vuejs | core | 687,715,226 | 2,057 | HcySunYang | Currently, there is a binding relationship between the `computed` and component `instance`, so that `computed`'s effect will be `stopped` when the component is `unmounted`. The singleton makes computed's effect never activate again after being stopped, maybe we need to add an option for `computed()`, such as `global`:
... | 2020-09-06T07:22:10 | 2020-09-06T07:22:10 | {} | MEMBER |
vuejs | core | 683,833,767 | 2,013 | FrankFang | I've updated the demo: https://codepen.io/FrankFang/pen/dyMzOBd?editors=0010
It's a simple tab switcher with a bug.
1. click tab 1
2. click tab 2
expected: content changes
fact: content never changes | 2020-08-31T14:59:36 | 2020-08-31T15:01:44 | {} | NONE |
vuejs | core | 684,079,196 | 2,018 | yyx990803 | This is expected behavior. | 2020-08-31T22:37:57 | 2020-08-31T22:37:57 | {} | MEMBER |
vuejs | core | 685,001,660 | 2,013 | yyx990803 | When using `<component :is="vnode">` and passing vnode of the same type, you need to provide keys:
```html
<component :is="current" :key="selected" />
```
Otherwise, you are passing two **compiled** vnodes of the same type to the renderer. Because they are compiled as completely static, they will not be updated... | 2020-09-01T17:00:59 | 2020-09-01T17:00:59 | {
"+1": 28
} | MEMBER |
vuejs | core | 685,070,558 | 2,018 | nerdcave | It's not that I need to prevent it from happening, necessarily, it's more about making sure it's not some bug or gotcha that should be further documented I guess? This specific scenario just struck me as a bit unintuitive. | 2020-09-01T19:00:08 | 2020-09-01T19:00:08 | {} | NONE |
vuejs | core | 685,255,729 | 2,027 | rothskeller | @yyx990803 Your response makes sense, but permit me to note that it disagrees with the documentation for view-router-next, which explicitly calls for watching the route object. I do not know how to reconcile between two core Vue projects. | 2020-09-02T02:53:22 | 2020-09-02T02:53:22 | {
"+1": 3
} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.