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 | 690,003,439 | 2,086 | 07akioni | > This has already been fixed: [ac81dcf](https://github.com/vuejs/vue-next/commit/ac81dcf0cc7f5fc722a0c14d1cc92ece5cc0db07), please wait for the new release.
The commit seems already been released in rc.10. How does it be fixed?
node_modules/...
![image](https://user-images.githubusercontent.com/18677354/9268732... | 2020-09-10T05:53:03 | 2020-09-10T06:08:31 | {} | CONTRIBUTOR |
vuejs | core | 690,024,495 | 2,081 | vallemar | That does not work. Also, I can't find what you say in the documentation. `input` is a native element, it is not a custom component.
Anyway, it doesn't make sense that it works on PC and not on mobile browsers. If this were a change it would not work on any platform or browser. | 2020-09-10T06:42:30 | 2020-09-10T06:44:41 | {
"+1": 1
} | NONE |
vuejs | core | 689,914,308 | 2,080 | lanezhao | Simply change `<template>` to `<div>` or remove ':key="item.id"' will avoid the problem.
Disallow key attribute on `<template>`
https://eslint.vuejs.org/rules/no-template-key.html | 2020-09-10T01:23:41 | 2020-09-10T07:26:59 | {} | NONE |
vuejs | core | 691,307,310 | 2,101 | 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-09-11T20:54:37 | 2020-09-11T20:54:37 | {} | CONTRIBUTOR |
vuejs | core | 691,411,587 | 1,166 | syuilo | Is there any migration strategy for about this? | 2020-09-12T05:06:00 | 2020-09-12T05:06:00 | {
"eyes": 2
} | CONTRIBUTOR |
vuejs | core | 688,162,936 | 2,064 | posva | Is this a problem in rollup-plugin-vue @znck ? | 2020-09-07T08:33:59 | 2020-09-07T08:33:59 | {} | MEMBER |
vuejs | core | 688,179,359 | 2,064 | skyweaver213 | > What do you mean? the component is named `HelloWorld` and used as `<HelloWorld/>`
The source code is \<HelloWorld msg="Hello Vue in Fenice!" /\>
Source link: https://codesandbox.io/s/cocky-noyce-6zi8p?file=/pages/home/App.vue:56-98
>
> The reason is simple, only when component define prop inside self, the outside prop can be prop value of component instance
Sadly, it does't work w... | 2020-09-07T12:42:08 | 2020-09-07T12:42:08 | {} | NONE |
vuejs | core | 690,009,355 | 2,085 | amrnn90 | @lanezhao
In Vue 3 using `key` is valid with `<template v-for>` | 2020-09-10T06:06:37 | 2020-09-10T06:06:37 | {} | NONE |
vuejs | core | 690,107,405 | 2,084 | posva | This was asked for Vue 2 https://github.com/vuejs/vue/issues/8028 | 2020-09-10T09:21:27 | 2020-09-10T09:21:27 | {
"heart": 1
} | MEMBER |
vuejs | core | 690,976,215 | 2,078 | posva | @CyberAP Can you post the whole code you used? It doesn't seem to work | 2020-09-11T09:15:42 | 2020-09-11T09:15:42 | {} | MEMBER |
vuejs | core | 691,622,693 | 2,105 | luthfimasruri | **Yes!!**
**Here's Reproduction link:**
https://github.com/luthfimasruri/vue3-ts.git
It happens in reactive as well | 2020-09-13T06:46:38 | 2020-09-13T06:48:09 | {} | NONE |
vuejs | core | 691,622,969 | 2,105 | stefnotch | That's not a bug, that's intentional behavior, like the documentation says. You want `v-model.number="num1"`.
> According to vue3 docs, "Refs infer the type from the initial value", but it behaves as a string.
That refers to Typescript, which is purely for the IDE. | 2020-09-13T06:50:28 | 2020-09-13T06:50:28 | {} | NONE |
vuejs | core | 688,166,463 | 1,790 | skirtles-code | @CyberAP I don't think your example would be affected as it doesn't include any props.
@jods4 I did a bit of digging to try to understand this better. Here is my (very rough) explanation of what is going on.
There are two ways that a component update (re-render) can be triggered in Vue 3.
Firstly, if any react... | 2020-09-07T08:39:35 | 2020-09-07T08:39:35 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 688,930,568 | 2,018 | bzd2000 | hi @yyx990803 ,
That it is indeed what I want to achieve. So maybe misunderstood the props then.
when I update the string in the child, the string in the parent **is not** updated.
when I update the array in the child, the array in the parent **is** updated.
I would expect that both props behave in the same way... | 2020-09-08T14:51:22 | 2020-09-08T14:58:02 | {} | NONE |
vuejs | core | 689,900,720 | 2,081 | lanezhao | Modify `<input v-model="text">` to `<input v-model:value="text">`
Please read
https://v3.vuejs.org/guide/migration/v-model.html#v-model | 2020-09-10T00:43:20 | 2020-09-10T00:43:20 | {} | NONE |
vuejs | core | 690,105,030 | 2,081 | posva | > I have checked in the documentation for Vue 2 and the error is also present.
Because it's intended. It's not an error. Please search existing issues in vue repo for deeper explanations.
Without that fix we have, the value of v-model would become any intermediary steps. In Spanish, it would be while typing accen... | 2020-09-10T09:16:54 | 2020-09-10T09:16:54 | {} | MEMBER |
vuejs | core | 690,134,457 | 2,092 | posva | As said, provide a boiled down reproduction with no extra dependencies https://jsfiddle.net/n4890y27/
https://new-issue.vuejs.org/?repo=vuejs/vue-router-next#why-repro | 2020-09-10T10:15:01 | 2020-09-10T10:15:01 | {} | MEMBER |
vuejs | core | 690,191,470 | 2,083 | ConsoleTVs | @posva The thing is this happens if u call it on a normal value, not a ref.
ref(10) for example | 2020-09-10T11:31:04 | 2020-09-10T11:31:04 | {} | CONTRIBUTOR |
vuejs | core | 691,200,643 | 2,078 | posva | That won't work for `custom` ref though, it's like omitting the `ref` attribute | 2020-09-11T16:43:41 | 2020-09-11T16:43:41 | {} | MEMBER |
vuejs | core | 688,184,913 | 1,790 | jods4 | @skirtles-code Thanks for doing the digging, I hadn't looked deeply into these parts yet.
So as I understand your findings, it's not a correctness issue but rather ease of implementation:
that second direct update path would have a hard time determining if a change in the parent is or is not amongst the dependencie... | 2020-09-07T09:08:48 | 2020-09-07T09:08:48 | {} | CONTRIBUTOR |
vuejs | core | 688,217,428 | 2,064 | posva | it's weird because it works with vite | 2020-09-07T10:02:08 | 2020-09-07T10:02:08 | {} | MEMBER |
vuejs | core | 688,290,016 | 2,067 | 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/9108?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-09-07T12:22:10 | 2020-09-07T12:22:10 | {} | CONTRIBUTOR |
vuejs | core | 688,305,696 | 2,064 | HcySunYang | The reason is like @skirtles-code said, and should modify the `rollup.config.js` to solve that issue:
```js
// rollup.config.js
export default {
output: {
// ...
globals: { vue: 'Vue' }
},
// ...
external: ['vue']
}
``` | 2020-09-07T12:52:31 | 2020-09-07T12:52:31 | {
"+1": 2
} | MEMBER |
vuejs | core | 689,489,319 | 2,078 | CyberAP | It works for a `:ref` binding though. | 2020-09-09T11:03:45 | 2020-09-09T11:03:45 | {} | CONTRIBUTOR |
vuejs | core | 690,096,951 | 2,088 | haoqunjiang | Question: shall we fail gracefully if an error is thrown during parsing?
Because users may have configured custom babel plugins, and if they are not using `<script setup>`, they shouldn't have to understand how to configure the `babelParserPlugins` option. | 2020-09-10T09:01:49 | 2020-09-10T09:01:49 | {} | MEMBER |
vuejs | core | 690,637,605 | 2,096 | yyx990803 | The semantics of binding `class` to an object is [using its keys as classes to be displayed](https://v3.vuejs.org/guide/class-and-style.html#object-syntax). It would be a breaking change to use the `toString()` value instead. | 2020-09-10T19:08:08 | 2020-09-10T19:09:03 | {
"+1": 1
} | MEMBER |
vuejs | core | 690,878,952 | 2,097 | 07akioni | Let me explain more percisely.
pseudo code in vue 2/3
index
```
Vue2
import otherComponents from 'ui'
import MessagePlugin from 'message'
import Vue from 'vue'
Vue.use(otherComponents)
Vue.use(MessagePlugin)
Vue3
import otherComponents from 'ui'
import MessagePlugin from 'message'
import { createAp... | 2020-09-11T05:15:36 | 2020-09-11T05:32:36 | {} | CONTRIBUTOR |
vuejs | core | 691,551,383 | 2,105 | stefnotch | This should explain it
https://vuejs.org/v2/guide/forms.html#number | 2020-09-12T21:23:30 | 2020-09-12T21:23:30 | {} | NONE |
vuejs | core | 691,557,013 | 2,105 | luthfimasruri | No, even with `type="number"` the result still the same (5+2 = 52).
The code in typescript:
```
<script lang="ts">
import { defineComponent, onMounted, ref } from "vue";
export default defineComponent({
setup() {
const num1 = ref(2);
const num2 = ref(2);
const result = ref(0);
function add... | 2020-09-12T21:56:45 | 2020-09-12T22:07:19 | {} | NONE |
vuejs | core | 691,646,585 | 2,106 | posva | You probably need to follow the migration guide https://v3.vuejs.org/guide/migration/introduction.html#overview
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2020-09-13T09:44:00 | 2020-09-13T09:44:00 | {
"-1": 15
} | MEMBER |
vuejs | core | 691,647,889 | 2,108 | posva | We are aware of this pitfall and it's something we need to document for library authors.
@bencodezen I didn't transfer the issue because I imagine we want to write something different to track this at https://github.com/vuejs/docs-next | 2020-09-13T09:52:41 | 2020-09-13T09:52:41 | {} | MEMBER |
vuejs | core | 688,045,672 | 2,062 | HcySunYang | Use `markRaw()`:
```js
this.tl = Vue.markRaw(gsap.timeline({ paused: true }));
``` | 2020-09-07T05:31:25 | 2020-09-07T05:31:25 | {
"+1": 1
} | MEMBER |
vuejs | core | 690,015,842 | 2,086 | HcySunYang | Sorry, I provided the wrong link, it's here: https://github.com/vuejs/vue-next/commit/5f4053967cb61620d3dd27518f571166d7b5ec8f | 2020-09-10T06:22:00 | 2020-09-10T06:22:00 | {
"laugh": 1
} | MEMBER |
vuejs | core | 690,868,620 | 2,097 | lawvs | 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'), ...)) // Error ❌
// ... | 2020-09-11T04:37:39 | 2020-09-11T06:05:23 | {} | CONTRIBUTOR |
vuejs | core | 691,228,593 | 2,099 | CyberAP | > A timeout prop can be specified - if a pending tree remains pending past the timeout threshold, the active tree will be unmounted and be replaced by the fallback tree.
Would it be possible to add a new Composition hook for the cleanup?
```js
import { onTimeout } from 'vue'
export default {
setup() {
... | 2020-09-11T17:45:21 | 2020-09-11T17:45:53 | {} | CONTRIBUTOR |
vuejs | core | 691,472,342 | 2,102 | posva | Please open an issue at https://github.com/vitejs/vite | 2020-09-12T11:17:48 | 2020-09-12T11:17:48 | {} | MEMBER |
vuejs | core | 691,622,229 | 2,105 | stefnotch | > even with type="number", the value of HTML input elements always returns a string. | 2020-09-13T06:40:57 | 2020-09-13T06:40:57 | {} | NONE |
vuejs | core | 691,671,305 | 2,108 | CyberAP | You'll have to npm link vue in your composition library as well. Yes, that's disturbing. | 2020-09-13T13:25:54 | 2020-09-13T13:25:54 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 703,680,545 | 2,303 | langhuihui | 例如说我有个SFC
```
<template>
{{ text }}
<a-tag :color="color">{{ tag }}</a-tag>
</template>
<script>
export default {
props: {
text: String,
tag: String,
color: String,
},
};
</script>
```
这个渲染没问题
但如果我把这个组件的定义放到引用该组件的组件中
```
export default {
components: {
... | 2020-10-05T14:46:44 | 2020-10-05T14:46:44 | {} | NONE |
vuejs | core | 704,725,144 | 2,316 | martonlederer | I agree, that there are some trolls/spammers, but I think people wouldn't dare to do it in such a large repo + [shitoberfest](https://twitter.com/shitoberfest) only collects the worst examples, the majority of the participants are actually contributing | 2020-10-07T06:30:39 | 2020-10-07T06:30:39 | {} | NONE |
vuejs | core | 704,862,205 | 2,326 | unbyte | you can get the value of `modelModifiers` as prop, and turn value into number inside the component.
a bad example:
```js
app.component('custom-input', {
props: ["modelValue", "modelModifiers"],
template: `<input :value="modelValue" @input="$emit('update:modelValue', modelModifiers.number ? Number($event.targ... | 2020-10-07T11:05:47 | 2020-10-07T11:07:42 | {} | CONTRIBUTOR |
vuejs | core | 705,290,555 | 2,310 | edison1105 | It's fixed via f06518a8c9201b4fa2a956595aa9d89a192fcd20
so I close this PR. | 2020-10-08T02:19:54 | 2020-10-08T02:19:54 | {} | MEMBER |
vuejs | core | 706,639,826 | 2,350 | KaelWD | Isn't this intentional? You aren't supposed to use mixins with setup. | 2020-10-11T02:28:19 | 2020-10-11T02:28:19 | {} | CONTRIBUTOR |
vuejs | core | 706,721,666 | 2,349 | justintaddei | This would be very helpful my v-shared-element library as well. I hope this gets implemented! | 2020-10-11T15:27:04 | 2020-10-11T15:27:04 | {} | NONE |
vuejs | core | 706,714,278 | 2,353 | unbyte | gotcha.
but I wonder how it works for `:value`. The logic of set props is in `runtime-core`, but set props such as `min`, `max` before `value` is a unique logic of DOM. | 2020-10-11T14:38:01 | 2020-10-11T15:27:59 | {} | CONTRIBUTOR |
vuejs | core | 706,806,846 | 2,303 | langhuihui | @unbyte 上面的代码就是最小复现代码，很容易构造出来 | 2020-10-12T01:25:36 | 2020-10-12T01:25:36 | {} | NONE |
vuejs | core | 706,896,347 | 2,357 | cheqianxiao | @edison1105 Thanks for replying. your workaround works in the case above. but there is a case in which the paramerter passed to `resolveComponent` is dynamic:
```js
//value of tagName can be builtin html tag name such as 'div' or custom global component name 'my-button' for example.
// in the former situa... | 2020-10-12T06:24:26 | 2020-10-12T06:24:26 | {} | NONE |
vuejs | core | 704,340,341 | 1,242 | posva | Thanks @unbyte ! | 2020-10-06T15:13:38 | 2020-10-06T15:13:38 | {} | MEMBER |
vuejs | core | 705,170,322 | 2,261 | yyx990803 | Hmm, technically this isn't a leak, because a computed property creates an effect which needs to be stopped to release itself from all depMaps.
When you create a computed inside a component's `setup()`, its effect is automatically stopped when the component unmounts so the user don't need to think about it.
In yo... | 2020-10-07T20:16:58 | 2020-10-07T20:18:37 | {
"+1": 2
} | MEMBER |
vuejs | core | 705,393,986 | 2,331 | posva | You can do this: https://github.com/vuejs/vue-next/issues/629#issuecomment-700549376
BTW you shouldn't mount components inside other already mount component like you are showing in Vue 2 | 2020-10-08T07:45:07 | 2020-10-08T07:45:07 | {} | MEMBER |
vuejs | core | 706,964,603 | 2,360 | jacekkarczmarczyk | ```js
return {myChild,callMyChild}
``` | 2020-10-12T08:24:18 | 2020-10-12T08:24:18 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 704,332,184 | 1,242 | unbyte | @posva have tested with latest version, it works now. this issue can be closed | 2020-10-06T15:02:47 | 2020-10-06T15:02:47 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 704,758,631 | 2,300 | edison1105 | 
`accessCache` is incorrect when next code run.
`provide() {
return {
a: this.a
}
}
`
It should be `1`(`AccessTypes.DATA`) | 2020-10-07T07:45:12 | 2020-10-07T14:51:24 | {} | MEMBER |
vuejs | core | 705,651,350 | 2,329 | 69hunter | @LinusBorg This test covers the provide/inject in the 2 following ways:
- The component's `provide` will override parent's `provide`.
- The `provide` in the component's `mixin` will override parent's `provide`. | 2020-10-08T15:35:05 | 2020-10-08T15:35:05 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 705,984,641 | 2,327 | kleinfreund | The correct link is https://v3.vuejs.org/guide/component-provide-inject.html#working-with-reactivity. | 2020-10-09T05:56:53 | 2020-10-09T05:56:53 | {} | CONTRIBUTOR |
vuejs | core | 706,693,940 | 2,353 | unbyte | https://github.com/vuejs/vue-next/commit/54ed7592e416fc411196e9b767aebcc4f2ca20d8 ignored that `:value` also can cause #2325 , which is due to the order when initializing an element's attributes.
I believe similar problems may exist on other platforms, so I think it might be better to add `delayInitProp` to runtime-... | 2020-10-11T11:56:42 | 2020-10-11T11:56:42 | {} | CONTRIBUTOR |
vuejs | core | 706,701,293 | 2,353 | unbyte | I'm not sure if this change is appropriate in fact.
> Maybe looking through the vnode attrs to check if the value needs to be set one tick after instead of using mounted like in 54ed759 works
I've considered a similar approach, but when it comes to async prop initializing, it's hard to guarantee that there's no ... | 2020-10-11T12:59:03 | 2020-10-11T13:06:35 | {} | CONTRIBUTOR |
vuejs | core | 706,857,302 | 2,357 | edison1105 | `
const button = resolveComponent("my-button") as ComponentOptions;
`
as workround. | 2020-10-12T04:49:23 | 2020-10-12T04:49:50 | {} | MEMBER |
vuejs | core | 703,662,420 | 2,303 | yyx990803 | 看不懂你的问题，但是 Vue 一直都支持运行时编译，前提是用户使用了带运行时编译器的 Vue 版本。 | 2020-10-05T14:17:45 | 2020-10-05T14:17:45 | {} | MEMBER |
vuejs | core | 704,745,976 | 1,600 | antoniandre | Do we have a timeframe for this feature to be released?
Thanks! | 2020-10-07T07:18:03 | 2020-10-07T07:18:03 | {
"+1": 4
} | NONE |
vuejs | core | 705,172,219 | 2,263 | yyx990803 | See https://github.com/vuejs/vue-next/issues/2261#issuecomment-705170322
Although this does de-reference computed effects in **some** cases, it's not a complete guarantee as it requires the dependency to trigger the effect, and only clears it from the map of that specific dependency. It is still required to properly... | 2020-10-07T20:20:48 | 2020-10-07T20:21:23 | {} | MEMBER |
vuejs | core | 705,530,657 | 2,261 | basvanmeurs | Hi Evan, thanks for your response. I can see the advantage of using scopes, and I like that PR. However, it would make sense to be able to stop the computeds individually, as we can do with watchers.
| 2020-10-08T12:20:05 | 2020-10-08T12:20:05 | {} | CONTRIBUTOR |
vuejs | core | 705,549,495 | 2,329 | LinusBorg | could you add a little comment here what issue this tests for? | 2020-10-08T12:57:26 | 2020-10-08T12:57:26 | {} | MEMBER |
vuejs | core | 706,149,656 | 2,343 | LinusBorg | the issue is likely rooted in the fact that, similar to React, in our new virtual DOM design, we don't differentiate between, (Vue-)props, attributes and domProps (or events) - all are just propertiess on a
flat vnode object.
We handle this for normal DOM Element props/attributes internally during the patch phase... | 2020-10-09T12:23:07 | 2020-10-09T12:47:32 | {} | MEMBER |
vuejs | core | 707,026,688 | 2,363 | posva | Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions!
---
See https://v3.vuejs.org/guide/composition-api-setup.html#props: props cannot be destructured | 2020-10-12T10:13:46 | 2020-10-12T10:14:11 | {} | MEMBER |
vuejs | core | 703,883,793 | 2,281 | LinusBorg | You got it right 🙂 | 2020-10-05T20:55:51 | 2020-10-05T20:55:51 | {
"laugh": 1
} | MEMBER |
vuejs | core | 705,042,900 | 2,326 | 69hunter | This should be related to https://github.com/vuejs/vue-next/issues/1825 | 2020-10-07T16:14:30 | 2020-10-07T16:14:30 | {} | CONTRIBUTOR |
vuejs | core | 706,166,634 | 2,326 | lian-ders | >
>
> you can get the value of `modelModifiers` as prop, and turn value into number inside the component.
>
> a bad example:
>
> ```js
> app.component('custom-input', {
> props: ["modelValue", "modelModifiers"],
> template: `<input :value="modelValue" @input="$emit('update:modelValue', modelModifiers.n... | 2020-10-09T13:00:26 | 2020-10-09T13:00:26 | {} | NONE |
vuejs | core | 706,465,421 | 1,347 | bbugh | Having a slot for `#timeout` and/or integrating it with `#error` would be nice too. For example, in the case where an async query times out, we don't want to fall back to "loading..." again, we want it to show to the user that the operation took too long and died. | 2020-10-10T01:43:28 | 2020-10-10T01:43:28 | {} | NONE |
vuejs | core | 706,698,337 | 2,354 | mathieutu | The failing tests are about suspense and seem to be totally out of the scope of this PR. | 2020-10-11T12:34:11 | 2020-10-11T12:34:19 | {} | CONTRIBUTOR |
vuejs | core | 703,675,225 | 2,303 | langhuihui | 我使用的vite，安装vue@3.0.0，是否包含了运行时编译器呢？ | 2020-10-05T14:38:09 | 2020-10-05T14:38:09 | {} | NONE |
vuejs | core | 703,910,045 | 2,221 | yyx990803 | See f4119249 - I refactored the logic to avoid duplicated code/iterations. | 2020-10-05T21:54:26 | 2020-10-05T21:54:26 | {} | MEMBER |
vuejs | core | 706,725,416 | 2,355 | pcimcioch | This would be another workaround for this issue.
But what if `Counter` is third party class? Or I want `Counter` to be decoupled from vue library?
Vue supports such objects, by automatically wrapping object properties in proxy.
And it works in most cases. I just found this one corner case where it used to work in ... | 2020-10-11T15:54:16 | 2020-10-11T15:54:16 | {
"+1": 1
} | NONE |
vuejs | core | 703,300,132 | 2,298 | 07akioni | @posva https://codesandbox.io/s/vue-directive-bug-template-06oyx?file=/src/App.vue | 2020-10-04T18:59:19 | 2020-10-04T18:59:19 | {} | CONTRIBUTOR |
vuejs | core | 704,132,086 | 2,254 | edison1105 | closed this PR, because the repo of this PR is deleted.😂😂😂.
so I open a new PR https://github.com/vuejs/vue-next/pull/2308
| 2020-10-06T08:59:46 | 2020-10-06T08:59:46 | {
"laugh": 1
} | MEMBER |
vuejs | core | 705,269,756 | 2,305 | yyx990803 | 👍 | 2020-10-08T00:57:23 | 2020-10-08T00:57:23 | {} | MEMBER |
vuejs | core | 705,507,596 | 2,335 | 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/10098?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 tes... | 2020-10-08T11:28:25 | 2020-10-08T11:28:25 | {} | CONTRIBUTOR |
vuejs | core | 706,001,559 | 2,214 | edison1105 | It's not relate to reactive.
This bug is caused by the `patchFlag` of `VNode` is 0.
There is nothing to do in `patchElement` function when input value changed.
Maybe it's bad way to fix this, but works fine.😭😭😭 | 2020-10-09T06:41:31 | 2020-10-10T01:05:24 | {
"+1": 1
} | MEMBER |
vuejs | core | 706,554,320 | 2,141 | 07akioni | > Please use `getCurrentInstance`.
>
> ```ts
> import { getCurrentInstance } from 'vue'
>
> onMounted(() => {
> const instance = getCurrentInstance()
> })
> ```
Is there any way to typing the return value of `getCurrentInstance()`? | 2020-10-10T14:07:03 | 2020-10-10T14:07:03 | {} | CONTRIBUTOR |
vuejs | core | 706,663,579 | 2,350 | LeBenLeBen | @KaelWD That’s what I thought at first, but since the value is actually available it looks more like a bad typing to me. I don't think I’ve seen another way than mixins to share props definition between components. | 2020-10-11T07:30:08 | 2020-10-11T07:30:08 | {} | NONE |
vuejs | core | 703,919,856 | 2,287 | yyx990803 | See 5c3e8e98
`currentInstance` isn't always guaranteed to be correct in this case since `this.$nextTick` may get called at any timing. | 2020-10-05T22:19:46 | 2020-10-05T22:19:46 | {} | MEMBER |
vuejs | core | 705,549,152 | 2,333 | KaelWD | Duplicate of #2298? | 2020-10-08T12:56:45 | 2020-10-08T12:56:45 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 705,911,232 | 2,327 | edison1105 | > What is stopping you from doing what's said in [the example you provided](v3.vuejs.org/guide/component-provide-inject.html#working-with-reactivity)?
@posva this link is incorrect | 2020-10-09T01:23:32 | 2020-10-09T01:23:32 | {} | MEMBER |
vuejs | core | 706,713,525 | 2,355 | posva | You should declare your reactive values as such, e.g.:
```js
this.value = Vue.ref(0);
setInterval(() => {
this.value.value++;
}, 1000);
``` | 2020-10-11T14:32:29 | 2020-10-11T14:32:44 | {} | MEMBER |
vuejs | core | 703,299,386 | 2,298 | posva | @07akioni can you provide the actual template used to generate that render function instead of providing a render function? | 2020-10-04T18:53:13 | 2020-10-04T18:53:13 | {} | MEMBER |
vuejs | core | 704,582,578 | 2,290 | yyx990803 | Thanks for the PR, but I think it's better to limit the force trigger logic to shallow refs only (which was why it was introduced) so `isComputed` would also be unnecessary. See 390589ec | 2020-10-06T22:17:30 | 2020-10-06T22:17:30 | {} | MEMBER |
vuejs | core | 706,082,278 | 2,250 | varHarrie | This might be a way to share the props definition between components. | 2020-10-09T09:44:16 | 2020-10-09T09:44:16 | {} | NONE |
vuejs | core | 706,122,374 | 2,327 | LifeIsStrange | @posva *What is stopping you from doing what's said in the example you provided?*
Well the documentation said *we would need to assign a Composition API computed property to our provided todoLength*
so I thougth the composition was not acessible in the options api (without setup) but actually I tried it and it's work... | 2020-10-09T11:16:49 | 2020-10-09T11:16:49 | {} | NONE |
vuejs | core | 706,147,641 | 2,343 | LinusBorg | Related: https://github.com/vuejs/rfcs/blob/master/active-rfcs/0008-render-function-api-change.md#escape-hatches-for-explicit-binding-types | 2020-10-09T12:18:24 | 2020-10-09T12:18:24 | {} | MEMBER |
vuejs | core | 706,707,082 | 2,355 | pcimcioch | I think this may be connected to starting acync operation in constructor. As a workaround, this works correctly:
```
class Counter {
constructor() {
this.value = 0;
}
start() {
setInterval(() => {
this.value++;
}, 1000);
}
}
Vue.createApp({
da... | 2020-10-11T13:45:05 | 2020-10-11T13:45:05 | {} | NONE |
vuejs | core | 706,904,237 | 2,356 | posva | See https://github.com/vuejs/vue-router-next/issues/521 | 2020-10-12T06:39:02 | 2020-10-12T06:39:02 | {} | MEMBER |
vuejs | core | 703,706,569 | 2,303 | Justineo | 控制台的错误提示你都贴了……不看一下吗 | 2020-10-05T15:27:23 | 2020-10-05T15:27:23 | {} | MEMBER |
vuejs | core | 706,368,619 | 2,343 | robaxelsen | Thanks @graynorton. Yeah, hoping for an answer from the Stencil.js team too.
But also curious as to if this could have to do with state management patterns inside more complex web components, or some similar best practices across web components frameworks, due to custom-elements-everywhere.com and their mention of Vu... | 2020-10-09T19:39:49 | 2020-10-09T19:39:49 | {} | NONE |
vuejs | core | 703,471,231 | 2,300 | posva | As a workaround, you can use `this.$data.a` inside of `updated` | 2020-10-05T08:03:14 | 2020-10-05T08:03:14 | {} | MEMBER |
vuejs | core | 704,724,049 | 2,316 | LinusBorg | Considering how Hacktoberfest is going this year (see: https://twitter.com/shitoberfest), I personally think we should not put a spotlight on this repository for now.
| 2020-10-07T06:28:13 | 2020-10-07T06:28:13 | {
"+1": 2
} | MEMBER |
vuejs | core | 704,882,025 | 2,327 | posva | What is stopping you from doing what's said in [the example you provided](http://v3.vuejs.org/guide/component-provide-inject.html#working-with-reactivity)? | 2020-10-07T11:49:51 | 2020-10-09T06:12:33 | {} | MEMBER |
vuejs | core | 706,011,228 | 2,341 | posva | Don't open issues without boiled down reproductions. Open a new issue once you have a boiled down reproduction on a jsfiddle | 2020-10-09T07:06:08 | 2020-10-09T07:06:08 | {} | MEMBER |
vuejs | core | 706,375,001 | 2,343 | graynorton | @robaxelsen It doesn't look like the tests for custom-elements-everywhere have been updated for Vue 3.0 yet, so I'd guess that the descriptive text hasn't been either.
I haven't looked at the Vue source and would be curious what @LinusBorg has to say, but it *appears* to me that Vue is no longer passing data to cust... | 2020-10-09T19:55:39 | 2020-10-09T19:55:39 | {
"+1": 1
} | NONE |
vuejs | core | 706,419,421 | 2,343 | graynorton | I was curious, so played around a bit more.
It appears that when binding into a CE, Vue 3.0 will bind to a property if the CE has a property descriptor or a setter for the corresponding name; otherwise, it will bind to an attribute. This seems like a good behavior; it essentially means that Vue will prefer binding t... | 2020-10-09T22:09:17 | 2020-10-09T22:09:17 | {
"+1": 4
} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.