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 | 663,838,976 | 1,696 | KaelWD | Vue 2 uses `this.$el` to determine if the mount target contains server-rendered content:
https://github.com/vuejs/vue/blob/d9b27a92bd5277ee23a4e68a8bd31ecc72f4c99b/src/core/instance/lifecycle.js#L67-L69
https://github.com/vuejs/vue/blob/bd6cea0973247e2a8e1d4a2250614c0bf44f0b26/src/core/vdom/patch.js#L719-L726 | 2020-07-25T10:25:35 | 2020-07-25T10:25:35 | {} | CONTRIBUTOR |
vuejs | core | 665,206,103 | 1,712 | yyx990803 | The root cause is because you are giving both branches of the `v-if` the same key, so when being patched both branches are considered the same component, and `placeholder` is a static prop so it's not patched at all.
This has to do with how `v-if` and `v-else` now behaves differently in v3 where different branches m... | 2020-07-28T18:32:24 | 2020-07-28T18:43:22 | {} | MEMBER |
vuejs | core | 661,725,153 | 1,664 | a1mersnow | @posva Have you followed my steps to reproduce?
Especially step 5 & 6
Try some times you will see it…… | 2020-07-21T08:49:57 | 2020-07-21T08:51:06 | {} | NONE |
vuejs | core | 662,034,107 | 1,671 | 509dave16 | @yyx990803 Completely understand your situation with Vue 3. The same transition is happening in the React ecosystem to move away from HOCs and to hooks instead in a lot of packages. `@apollo/client` is a prime example where in version 3, HOCs are deprecated and will no longer be maintained. HOCs are just my preferred ... | 2020-07-21T18:32:53 | 2020-07-21T18:51:58 | {} | NONE |
vuejs | core | 663,538,285 | 1,697 | yoyoys |
> make sure you also read the new docs:
> https://v3.vuejs.org/api/built-in-components.html#transition
> https://v3.vuejs.org/guide/transitions-overview.html#class-based-animations-transitions
> @yoyoys see [vuejs/rfcs#105](https://github.com/vuejs/rfcs/pull/105)
Thanks.
I've noticed that I can't use transitio... | 2020-07-24T13:27:59 | 2020-07-24T13:27:59 | {
"+1": 2
} | NONE |
vuejs | core | 665,010,656 | 1,699 | Benoit-Vasseur | Thanks :).
I was developping this and wanted to make a PR but it is done so it is perfect :).
However I have a suggestion concerning the v-model on a custom element.
I think it could be safer to force the "type" and name the prop `v-model-type` instead of type. type looks to dangerous to me for the naming collisio... | 2020-07-28T12:29:15 | 2020-07-28T12:29:15 | {} | NONE |
vuejs | core | 665,235,420 | 1,684 | yyx990803 | Thanks, the original commit has been amended in ba17c871 | 2020-07-28T19:34:40 | 2020-07-28T19:34:40 | {
"+1": 1
} | MEMBER |
vuejs | core | 661,725,584 | 1,532 | jods4 | @vmihailenco It does a lot of things.
`effect` from reactivity is basically `watchEffect`. | 2020-07-21T08:50:44 | 2020-07-21T08:50:44 | {} | CONTRIBUTOR |
vuejs | core | 661,903,138 | 1,661 | bjarkihall | Sure thing, I didn't want to affect the production performance since this had the "close to no-op" comment. :)
I updated the PR. | 2020-07-21T14:41:31 | 2020-07-21T14:41:31 | {} | CONTRIBUTOR |
vuejs | core | 665,109,753 | 1,728 | yyx990803 | I don't really think this is necessary. If you have a custom input element that is expected to work with `v-model` and have something like `type="radio"` or `type="checkbox"` on it, it would be **really** weird for it to not indicate that "this element behaves like a native radio/checkbox".
Adding yet another built-... | 2020-07-28T15:30:58 | 2020-07-28T15:30:58 | {} | MEMBER |
vuejs | core | 665,206,170 | 1,714 | yyx990803 | https://github.com/vuejs/vue-next/issues/1712#issuecomment-665206103 | 2020-07-28T18:32:33 | 2020-07-28T18:32:33 | {} | MEMBER |
vuejs | core | 665,246,555 | 1,438 | yyx990803 | This is something that we'd like to find a good solution for but it should probably go through the RFC process instead of being discussed here. | 2020-07-28T19:53:57 | 2020-07-28T19:53:57 | {} | MEMBER |
vuejs | core | 661,734,159 | 1,664 | posva | Now I managed to reproduce it, it only happens when doing the _undo_ action, not when changing the name to something else | 2020-07-21T09:07:01 | 2020-07-21T09:08:25 | {} | MEMBER |
vuejs | core | 662,318,042 | 1,677 | 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/7469?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-07-22T08:25:50 | 2020-07-22T08:25:50 | {} | CONTRIBUTOR |
vuejs | core | 663,178,417 | 1,657 | yyx990803 | 1. You can detect a functional component by simply checking `typeof comp === 'function'`. Async components are stateful (created with `defineComponent` internally).
2. In `mount`, you can simply always wrap the functional component to intercept `emits`. Just make sure to copy all additional properties on the functio... | 2020-07-23T19:01:07 | 2020-07-23T19:01:45 | {} | MEMBER |
vuejs | core | 663,332,105 | 1,686 | underfin | I think this is a bug.This will be fixed if we don't reuse dom for unkeyed children, but I'm not sure for this.
https://github.com/vuejs/vue-next/blob/3d2bdafd2fabe3aff5bec2eeaa9213f298ea52e8/packages/runtime-core/src/renderer.ts#L1527-L1574 | 2020-07-24T03:31:47 | 2020-07-24T03:34:37 | {} | MEMBER |
vuejs | core | 663,465,036 | 1,695 | posva | At that point, you should be able to directly create a Proxy around a reactive object | 2020-07-24T10:03:43 | 2020-07-24T10:03:43 | {} | MEMBER |
vuejs | core | 663,495,517 | 1,697 | posva | Please, don't create the issue before creating the reproduction. Only open the issue once you have a reproduction ready and published | 2020-07-24T11:31:58 | 2020-07-24T11:31:58 | {} | MEMBER |
vuejs | core | 663,498,156 | 1,697 | yoyoys | @posva sorry i've missing 2.x code, i'd pushed.
here is gif version
2.x
3.x
![2020-07-24 19 37 52](https://user-images.githubusercontent.com/22124891/88387628-71e10a80-cde5-11ea-984c-03bce... | 2020-07-24T11:39:55 | 2020-07-24T11:43:25 | {} | NONE |
vuejs | core | 663,509,421 | 1,697 | yoyoys | @posva do i need to submit a new issue? | 2020-07-24T12:14:28 | 2020-07-24T12:14:28 | {} | NONE |
vuejs | core | 664,407,757 | 1,721 | posva | It works with the actual code you posted. The problem is that you are hoisting the object with `{ innerHTML: this.val }` instead of passing a fresh one inside of the `default` slot function. Evan will probably give better feedback on this but I doubt you should write patch flags manually. I imagine you are aware of [th... | 2020-07-27T13:48:37 | 2020-07-27T13:48:37 | {} | MEMBER |
vuejs | core | 665,757,487 | 1,734 | IonianPlayboy | I see, thanks for the explanation ! It sure is more readable than having to wrap the v-if on the child, and it works just fine.
Can we expect to have the ESlint default config to be updated to handle this syntax, though ? (I have the `"plugin:vue/base"` and `"plugin:vue/vue3-recommended"` enabled) When I put the `ke... | 2020-07-29T16:10:33 | 2020-07-29T16:11:25 | {} | NONE |
vuejs | core | 666,258,948 | 1,706 | skirtles-code | @yyx990803 My apologies. In my attempt to be concise I failed to explain myself clearly.
My test case was only designed to illustrate the problem, it certainly wasn't a compelling example of correct `watch` usage. By the time I had stripped it down to a minimal example it did indeed appear to be a classic case of `w... | 2020-07-30T09:31:58 | 2020-07-30T09:31:58 | {
"+1": 3,
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 661,824,390 | 1,657 | lmiller1990 | I don't think the second case is very common or cause for concern (maybe I don't fully understand the example).
Here is the main problem I see (first case described above). [Reproduction here](https://github.com/vuejs/vue-test-utils-next/compare/functional-comoponent-emit?expand=1).
```js
it('capture emitted e... | 2020-07-21T12:25:55 | 2020-07-21T12:26:49 | {} | MEMBER |
vuejs | core | 661,893,547 | 1,645 | bjarkihall | @yyx990803 it makes total sense, but what doesn't make sense is that `defineComponent` type is an intersection of both `ComponentPublicInstanceConstructor` and `FunctionalComponent` type - since `defineComponent` doesn't ever return a `FunctionalComponent` in the implementation.
Also, can't JSX.Elements have a stric... | 2020-07-21T14:25:19 | 2020-07-21T14:25:19 | {} | CONTRIBUTOR |
vuejs | core | 663,534,160 | 1,697 | posva | @yoyoys see https://github.com/vuejs/rfcs/pull/105 | 2020-07-24T13:18:34 | 2020-07-24T13:18:34 | {
"+1": 1
} | MEMBER |
vuejs | core | 663,534,932 | 1,697 | pikax | make sure you also read the new docs:
https://v3.vuejs.org/api/built-in-components.html#transition
https://v3.vuejs.org/guide/transitions-overview.html#class-based-animations-transitions | 2020-07-24T13:20:24 | 2020-07-24T13:20:24 | {
"eyes": 1
} | MEMBER |
vuejs | core | 663,834,477 | 1,700 | Picknight | Sorry, I misunderstood your question. My fault. Let me see what I can do to help you. @jfet97 | 2020-07-25T09:34:15 | 2020-07-25T09:34:15 | {} | CONTRIBUTOR |
vuejs | core | 664,621,035 | 1,706 | yyx990803 | This is intended and expected behavior.
> However, that seems like a strange default as a watch (when used via the options API) will generally make some kind of data change that will require further rendering updates.
Your understanding is exactly the opposite of the intended design: watchers are intended for per... | 2020-07-27T20:28:13 | 2020-07-27T20:29:10 | {
"+1": 4
} | MEMBER |
vuejs | core | 664,979,253 | 1,727 | posva | You can pass the `{ flush: 'sync' }` option to recreate that behavior you want. This comment https://github.com/vuejs/vue-next/issues/1706#issuecomment-664621035 should be relevant to you | 2020-07-28T11:11:26 | 2020-07-28T11:11:26 | {} | MEMBER |
vuejs | core | 665,112,364 | 1,722 | yyx990803 | The WIP docs is wrong and needs to be updated. `attrs` and `slots` are not reactive. | 2020-07-28T15:35:39 | 2020-07-28T15:35:39 | {} | MEMBER |
vuejs | core | 665,493,270 | 1,730 | posva | This compilation error is intended. See https://github.com/vuejs/vue-next/issues/1712#issuecomment-665206103 | 2020-07-29T07:41:56 | 2020-07-29T07:41:56 | {} | MEMBER |
vuejs | core | 661,990,093 | 1,666 | yyx990803 | I realized we should avoid using bail flags since it affects how children are handled. See 6390ddfb | 2020-07-21T17:12:16 | 2020-07-21T17:12:16 | {} | MEMBER |
vuejs | core | 662,054,656 | 1,669 | yyx990803 | The filename should be absolute path for correct import resolution. | 2020-07-21T19:14:01 | 2020-07-21T19:14:01 | {} | MEMBER |
vuejs | core | 662,770,865 | 1,676 | yyx990803 | It's intentional. Non-enumerable properties should not be compared. | 2020-07-23T01:01:30 | 2020-07-23T01:01:37 | {} | MEMBER |
vuejs | core | 663,502,328 | 1,695 | amrnn90 | @posva Yes, guess that's the best way to do it right now. I was worried that maybe it would lead to reactivity issues since the outer proxy is not created by vue, but I guess since everything is eventually proxied to a reactive object then it should work fine.
@pikax Can you please show an example of how it might b... | 2020-07-24T11:53:11 | 2020-07-24T11:53:11 | {} | NONE |
vuejs | core | 663,829,855 | 1,696 | Timmitry | Hm, but in Vue 2, it seems that `this.$el` DID refer to the `div#app` in the `beforeMounted`-hook - as the code is working, see [the example I included](https://jsfiddle.net/8tkzdrwu/). Including the `data-title` attribute in the `template` does not really help, as we can't modify the template from our Rails-rendering,... | 2020-07-25T08:45:22 | 2020-07-25T08:45:38 | {} | NONE |
vuejs | core | 664,670,636 | 1,719 | yyx990803 | See 5fbd1f4c | 2020-07-27T22:29:34 | 2020-07-27T22:29:34 | {} | MEMBER |
vuejs | core | 666,675,055 | 1,741 | yyx990803 | Because in case 2 `style` is a static binding so it never gets updated. If you want to force update, use a dynamic binding. | 2020-07-30T20:29:09 | 2020-07-30T20:29:09 | {} | MEMBER |
vuejs | core | 731,015,750 | 2,642 | ljcremer | +1 for this | 2020-11-20T08:13:19 | 2020-11-20T17:42:14 | {} | NONE |
vuejs | core | 734,704,528 | 1,553 | tcastelly | > We don't have this implemented for typing yet, since it actually relies on the [template literal types](https://github.com/microsoft/TypeScript/pull/40336) feature which (I think) is going to be part of TS 4.1.
TS 4.1 has been released, I still have the error. Do you think it's possible to use the template literal... | 2020-11-27T08:11:56 | 2020-11-27T08:11:56 | {} | NONE |
vuejs | core | 735,411,578 | 2,686 | HcySunYang | You should check this https://github.com/vuejs/vue-next/issues/1995 | 2020-11-29T15:29:40 | 2020-11-29T15:29:40 | {} | MEMBER |
vuejs | core | 731,592,667 | 2,474 | JensDll | I would like to add that this is a design limitation in TypeScript; see this issue microsoft/TypeScript#38845. And I believe that the example under [Annotating Props](https://v3.vuejs.org/guide/typescript-support.html#annotating-props) in the docs will have this problem as well. | 2020-11-21T15:17:16 | 2020-11-21T15:28:57 | {} | CONTRIBUTOR |
vuejs | core | 731,959,695 | 2,660 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.28 KB (0%) |
| runtime-dom.global.prod.js | 26.51 KB (0%) |
| size-check.global.prod.js | 16.08 KB (0%) | | 2020-11-23T06:40:31 | 2020-11-25T16:21:31 | {} | NONE |
vuejs | core | 731,959,215 | 2,658 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.28 KB (0%) |
| runtime-dom.global.prod.js | 26.51 KB (0%) |
| size-check.global.prod.js | 16.08 KB (0%) | | 2020-11-23T06:39:16 | 2020-11-25T16:21:36 | {} | NONE |
vuejs | core | 734,378,820 | 629 | Danroyal001 | Alternatively, use class-style components
`import Vue from 'vue'`
`import Component from 'vue-class-component'`
`// Define the component in class-style`
`@Component`
`export default class Counter extends Vue {`
` // Class properties will be component data`
` count = 0`
` // Methods will be component me... | 2020-11-26T16:03:04 | 2020-11-26T16:08:55 | {} | NONE |
vuejs | core | 734,740,132 | 2,675 | posva | I think that what you are looking for is https://vuejs.github.io/vetur/vti.html and https://github.com/znck/vue-developer-experience | 2020-11-27T09:34:00 | 2020-11-27T09:34:00 | {} | MEMBER |
vuejs | core | 734,752,695 | 2,675 | znck | VueDX requires `defineComponent()` for prop type checking. | 2020-11-27T10:01:52 | 2020-11-27T10:01:52 | {} | MEMBER |
vuejs | core | 734,862,923 | 2,675 | znck | You can create and an issue on the VueDX repo with an example. | 2020-11-27T14:33:40 | 2020-11-27T14:33:40 | {} | MEMBER |
vuejs | core | 734,892,377 | 1,350 | fredrivett | Thanks so much for the swift reply here @posva.
I was actually looking at that SO post earlier today, and believe I've set everything correctly (though I may be being a dumbass).
My code above was a simplified example, my actual code that's not working is:
```
<input
v-model.trim="computedInput"
ref="in... | 2020-11-27T15:46:25 | 2020-11-27T15:46:25 | {} | NONE |
vuejs | core | 735,566,706 | 2,027 | white-007 | Close vue-devtools and the warning will disappear. This should be the problem with DevTools | 2020-11-30T05:59:05 | 2020-11-30T05:59:05 | {
"+1": 14
} | NONE |
vuejs | core | 731,121,471 | 2,649 | edison1105 | > Okay thanks for the hint 👍 I'll add it quickly to peerDependencies again. Actually it's not devDependencies 🤦 Sorry for confusion 🙃
If `postcss` add to `dependencies`, there is no need to add it to `peerDependencies`.
add it to both `devDependencies` and `peerDependencies` and then it makes sense.
If my und... | 2020-11-20T11:44:05 | 2020-11-20T11:44:05 | {
"+1": 2
} | MEMBER |
vuejs | core | 731,596,139 | 2,474 | yyx990803 | /cc @vuejs/docs | 2020-11-21T15:45:42 | 2020-11-21T15:45:42 | {} | MEMBER |
vuejs | core | 731,721,817 | 2,655 | posva | Wouldn't this be a breaking change for users with TypeScript < 4? It would be perfect if it could be introduced without breaking usage for TS 3.x | 2020-11-22T09:37:51 | 2020-11-22T09:38:28 | {} | MEMBER |
vuejs | core | 732,732,067 | 2,661 | posva | I find this a bit fragile and more implicit that passing slots through components in between the parent and its children because any component in between could use the slot name in the middle of the chain, and those could be toggled dynamically, ending up in quite confusing patterns.
In any case, this should go thro... | 2020-11-24T08:15:48 | 2020-11-24T08:17:09 | {} | MEMBER |
vuejs | core | 734,101,667 | 2,509 | kdeun1 | Hello.
I think you want to make `shallowRef` react.
Wouldn't the trigger work with `triggerRef(component);`? | 2020-11-26T06:27:30 | 2020-11-26T06:28:12 | {} | NONE |
vuejs | core | 735,301,629 | 2,684 | posva | No, you have to either disable attribute inheritance or declare the `emits` option https://v3.vuejs.org/guide/migration/emits-option.html | 2020-11-28T23:00:32 | 2020-11-28T23:00:32 | {
"+1": 1
} | MEMBER |
vuejs | core | 734,210,221 | 2,674 | posva | This is expected, you are overwriting the variable instead of changing it's content. Use a ref instead:
```js
let list = Vue.ref([1, 2, 3])
const handleDelete = item => {
// This is work
// const index = list.value.indexOf(item)
// if (index !== -1) list.value.splice(index, 1)
list... | 2020-11-26T10:20:19 | 2020-11-26T10:20:19 | {} | MEMBER |
vuejs | core | 734,210,765 | 2,649 | posva | @songololo I unlocked so you can post it 🙂 Thanks! | 2020-11-26T10:21:23 | 2020-11-26T10:21:23 | {
"+1": 1
} | MEMBER |
vuejs | core | 734,191,314 | 2,670 | nfplee | After further research I believe this scenario should be supported. I've just tested it in Vue 2 and it works fine. https://jsfiddle.net/cydnhpu6/, therefore it is a regression.
However I was able to fix this in Vue 3 by unmounting the instance. See https://jsfiddle.net/3amdpyjq/ for an updated examle. | 2020-11-26T09:44:55 | 2020-11-26T12:46:48 | {} | NONE |
vuejs | core | 734,878,964 | 1,350 | posva | The attribute is being set properly. You might need other attributes: https://stackoverflow.com/questions/254712/disable-spell-checking-on-html-textfields | 2020-11-27T15:10:37 | 2020-11-27T15:10:37 | {} | MEMBER |
vuejs | core | 731,457,904 | 2,653 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js). | 2020-11-20T23:24:05 | 2020-11-20T23:24:05 | {} | MEMBER |
vuejs | core | 732,695,291 | 2,666 | edison1105 | see https://github.com/vuejs/jsx-next | 2020-11-24T06:58:20 | 2020-11-24T06:58:20 | {} | MEMBER |
vuejs | core | 732,846,844 | 2,448 | edison1105 | > TARGET: 'reactivity', FORMATS: 'cjs', esm-bundler: 'true'
Nice to know this. | 2020-11-24T11:16:29 | 2020-11-24T11:16:29 | {} | MEMBER |
vuejs | core | 734,148,999 | 2,671 | posva | Looks like the `ref` is pointing to the AsyncWrapper instead | 2020-11-26T08:23:24 | 2020-11-26T08:23:24 | {} | MEMBER |
vuejs | core | 735,221,020 | 2,684 | posva | You need `inheritAttrs: false` in `Child.vue`. This is documented: https://v3.vuejs.org/guide/component-attrs.html#attribute-inheritance | 2020-11-28T11:45:13 | 2020-11-28T11:45:26 | {} | MEMBER |
vuejs | core | 731,366,531 | 2,648 | yassilah | Sorry about that, i just created the issue: #2652 ! | 2020-11-20T19:32:22 | 2020-11-20T19:32:22 | {} | CONTRIBUTOR |
vuejs | core | 732,681,332 | 2,665 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.39 KB (0%) |
| runtime-dom.global.prod.js | 26.5 KB (0%) |
| size-check.global.prod.js | 16.08 KB (0%) | | 2020-11-24T06:25:00 | 2020-11-24T06:25:00 | {} | NONE |
vuejs | core | 733,802,290 | 2,670 | posva | You can't manually manipulate the HTML at the same time you make Vue control it. To avoid this kind of problem, wrap vanilla JS inside a component but you can't use both at the same time
| 2020-11-25T16:10:38 | 2020-11-25T16:10:38 | {} | MEMBER |
vuejs | core | 734,130,091 | 2,673 | ghost | 报错依旧需要 vue-template-compiler
Module Error (from ./node_modules/vue-loader/lib/index.js):
[vue-loader] vue-template-compiler must be installed as a peer dependency, or a compatible compiler implementation must be passed via options.
@ ./src/main.js 6:0-28 7:10-13
@ multi (webpack)-dev-server/client?http://192.16... | 2020-11-26T07:39:55 | 2020-11-26T07:39:55 | {} | NONE |
vuejs | core | 734,147,671 | 2,673 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js).
---
`vue-template-compiler is for Vue 2. A freshly g... | 2020-11-26T08:20:40 | 2020-11-26T08:20:40 | {} | MEMBER |
vuejs | core | 731,479,406 | 2,513 | lucasforeman | I'm in a similar boat, not sure how much it's related to OP but it sounds very similar. I've a Vue.js app with an iframe, which loads a different Vue.js app. Sometimes, click events weren't registering in the nested app, commenting out the line highlighted in OP helped. It's weird because it didn't happen every time an... | 2020-11-21T00:58:12 | 2020-11-21T00:58:26 | {} | NONE |
vuejs | core | 731,975,352 | 2,657 | Alanscut | Using `props` may solve this issue, `props` is reactive.
```vue
// Child.vue
<template>
<div>props = {{ $props }}</div>
<div>props.active = {{ $props.active }}</div>
<div>computed(() => props.active) = {{ active1 }}</div>
</template>
<script>
import { computed, isReactive } from "vue";
export defa... | 2020-11-23T07:19:33 | 2020-11-23T07:19:33 | {} | CONTRIBUTOR |
vuejs | core | 733,829,055 | 2,670 | nfplee | @posva I've simplified my example but what I actually do is return back the HTML from an ajax call to the server and then try to wire up any Vue components in the returned string. It works the first time, but if the element has already been mounted via Vue then it doesn't work. | 2020-11-25T16:57:33 | 2020-11-25T16:57:33 | {} | NONE |
vuejs | core | 733,841,355 | 2,670 | posva | Ah, I see: you cannot mount an app inside of another app, you have to use components instead | 2020-11-25T17:19:48 | 2020-11-25T17:19:48 | {} | MEMBER |
vuejs | core | 735,430,186 | 803 | asv7c2 | Does this bug is fixed? I check with latest vue 3 version and nested ref is not unwrapped. Looks like in final version bug is returned. | 2020-11-29T17:44:50 | 2020-11-29T17:48:38 | {} | NONE |
vuejs | core | 735,578,947 | 2,689 | edison1105 | see https://github.com/vuejs/vue-class-component
But there is still some difference from what you expected | 2020-11-30T06:28:23 | 2020-11-30T06:28:23 | {} | MEMBER |
vuejs | core | 731,438,556 | 1,539 | soulsam480 | I also agree with @aztalbot.
Sometimes when we have a much dynamic template we need render functions.
e.g.
```javascript
render() {
return h("input", {
type: this.options.type,
class: this.options.className,
placeholder: this.options.holder,
id: this.options.id,
value: t... | 2020-11-20T22:24:56 | 2020-11-20T22:24:56 | {} | NONE |
vuejs | core | 734,161,574 | 2,671 | ShookLyngs | > Looks like the `ref` is pointing to the AsyncWrapper instead
Yes, and if I have a component `item`, its content is simply:
```
<template>
<slot />
</template>
```
Then when I use this component,
and pass a `async-component` to fill the slot:
```
<item>
<async-component />
</item>
```
In compo... | 2020-11-26T08:49:22 | 2020-11-26T08:49:22 | {} | NONE |
vuejs | core | 735,412,451 | 2,686 | lchrennew | > You should check this #1995
Thank you @HcySunYang very much. | 2020-11-29T15:36:18 | 2020-11-29T15:36:18 | {} | NONE |
vuejs | core | 731,092,239 | 2,649 | lstoeferle | > I'm not sure whether to do this.
I'm not sure if it makes sense adding it to both 🤔
| 2020-11-20T10:42:25 | 2020-11-20T10:42:25 | {} | NONE |
vuejs | core | 731,458,509 | 2,645 | Justineo | As @LinusBorg said, for loop here is intentional. Maybe we can explore faster approaches for looping through sets can maps but not the reverse (needs a performance benchmark). Thank you. | 2020-11-20T23:26:23 | 2020-11-20T23:26:23 | {} | MEMBER |
vuejs | core | 731,555,479 | 2,648 | yassilah | @LinusBorg I'm not quite sure how to add my test, I would either need a visual test or at least test if the element has the right namespace, but from what I saw, there is no namespaceURI on the TestElement class. | 2020-11-21T09:46:01 | 2020-11-21T09:46:01 | {} | CONTRIBUTOR |
vuejs | core | 733,618,584 | 2,668 | posva | As a workaround you can do `date: Date as PropType<Date>,` | 2020-11-25T10:29:10 | 2020-11-25T10:29:10 | {
"+1": 1
} | MEMBER |
vuejs | core | 734,328,470 | 1,600 | CyberAP | In the meantime, you can inject whitespace with this expression: `{{ ' ' }} `. Yes, it's not pretty but it works. | 2020-11-26T14:28:36 | 2020-11-26T14:28:36 | {
"+1": 3,
"-1": 2
} | CONTRIBUTOR |
vuejs | core | 734,343,776 | 1,600 | martinbean | @CyberAP My issue is, if I mount a Vue component on a wrapper div (usually `<div id="app">` in Laravel apps, it pretty much removes inline whitespace for _all_ elements in my website, as per the screenshot I added in an earlier message.
This changing of browser’s default whitespace handling is just unacceptable in m... | 2020-11-26T14:57:54 | 2020-11-26T14:57:54 | {} | NONE |
vuejs | core | 734,736,459 | 2,676 | posva | I think we should add a test in the `test-dts` folder | 2020-11-27T09:25:56 | 2020-11-27T09:25:56 | {} | MEMBER |
vuejs | core | 734,737,498 | 1,553 | tcastelly | @caohuatao
Thank you for your help, update the file `./node_modules/@vue/runtime-dom/dist/runtime-dom.d.ts` as bellow remove errors.
I guess it's a good workaround to avoid hundred errors :)
I'm looking forward to see a native solution to be able to keep types. | 2020-11-27T09:27:58 | 2020-11-27T09:27:58 | {} | NONE |
vuejs | core | 734,822,802 | 1,350 | fredrivett | This still seems to be an issue despite the fix merged on June 12th.
As I understand it, this should stop the spellchecker on iOS Safari:
`<input spellcheck="false" />`
Using the latest (`"vue": "^3.0.3"`) with `node_modules` and `yarn.lock` deleted and reinstalled, this error persists.
I've tried all other v... | 2020-11-27T12:56:33 | 2020-11-27T12:56:33 | {} | NONE |
vuejs | core | 735,237,303 | 2,684 | gerasimvol | It is. But isn't it unexpected that listeners are explicitly bound to wrong component? | 2020-11-28T14:25:59 | 2020-11-28T14:25:59 | {} | NONE |
vuejs | core | 731,780,471 | 2,540 | jw-foss | As I am making the UI library with my team, we received multiple bug reports from our users because of the changes against `emits`, and I am also confused by this.
The version of `Vue` I used is **v3.0.2**
My code here: [picker.vue](https://github.com/element-plus/element-plus/blob/dev/packages/time-picker/src/comm... | 2020-11-22T17:23:11 | 2020-11-23T03:02:10 | {} | NONE |
vuejs | core | 731,915,712 | 2,657 | robertmoura | > I believe this is intended, based on the docs.
Ah right. Do you know any ways to overcome these constraints? I'm using `onBeforeUpdate` at the moment. | 2020-11-23T04:07:34 | 2020-11-23T04:07:34 | {} | NONE |
vuejs | core | 732,920,508 | 2,667 | Korijn | Thanks for the workaround.
You've phrased it differently but essentially you are saying "indeed, wrapping inputs with attribute inheritance does not support v-model, unless you explicitly add support for it to the wrapping component (see example)", is that correct?
Would it be helpful if I open a PR to add this t... | 2020-11-24T12:04:08 | 2020-11-24T12:05:21 | {} | NONE |
vuejs | core | 734,890,056 | 2,648 | yassilah | I've added a test but still i'm a bit confused about the way Teleport works because:
- in my tests, i needed to add a v-if or disabled prop to the Teleport component because i otherwise get an error saying the destination is invalid; that's not the behaviour i get when trying it out outside of a test;
- it seems that... | 2020-11-27T15:40:05 | 2020-11-27T15:40:05 | {} | CONTRIBUTOR |
vuejs | core | 735,007,908 | 2,640 | yyx990803 | Thanks for the PR, but this is an incomplete fix. The more accurate fix is by detecting such cases at compile time. See 3bc2914 | 2020-11-27T23:05:49 | 2020-11-27T23:05:49 | {} | MEMBER |
vuejs | core | 731,958,370 | 2,561 | dependabot-preview[bot] | Superseded by #2658. | 2020-11-23T06:37:12 | 2020-11-23T06:37:12 | {} | CONTRIBUTOR |
vuejs | core | 731,959,457 | 2,659 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.39 KB (0%) |
| runtime-dom.global.prod.js | 26.5 KB (0%) |
| size-check.global.prod.js | 16.08 KB (0%) | | 2020-11-23T06:39:52 | 2020-11-23T06:39:52 | {} | NONE |
vuejs | core | 732,928,024 | 2,667 | posva | If you find a way to naturally introduce it (not a note/tip that breaks the flow), at https://v3.vuejs.org/guide/component-basics.html#using-v-model-on-components or somewhere else, I'm sure the docs team will appreciate! The idea is said there, though, v-model becomes an attribute an event listener, it's a convention. | 2020-11-24T12:09:05 | 2020-11-24T12:09:05 | {} | MEMBER |
vuejs | core | 733,617,464 | 2,669 | posva | Note `$attrs` doesn't contain the `data-v-...`. It would be inconvenient:
Parent component:
```vue
<template>
<input >
<CustomInput />
</template>
<style scoped>
input {
color: red;
}
```
CustomInput.vue:
```vue
<template>
<div>
<label>...</label>
<input v-bind="$attrs">
<div>
... | 2020-11-25T10:27:00 | 2020-11-25T10:27:00 | {} | MEMBER |
vuejs | core | 734,102,378 | 2,672 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.28 KB (0%) |
| runtime-dom.global.prod.js | 26.51 KB (0%) |
| size-check.global.prod.js | 16.08 KB (0%) | | 2020-11-26T06:29:31 | 2020-11-26T06:29:31 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.