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 | 714,365,163 | 2,455 | posva | See https://github.com/vuejs/vue/issues/11445
Please don't open bug reports without reproductions | 2020-10-22T09:34:02 | 2020-10-22T09:34:02 | {} | MEMBER |
vuejs | core | 714,372,635 | 2,456 | Jokcy | @posva
I did not find one issue that exactly match mine, besides, can you just give me an answer?
Is this by design?
So it mean if I want to use `ref` to attach dom element I have to use `flush: post` to watch it right?
I don't quite understand why you guys so eager to close issues. | 2020-10-22T09:46:27 | 2020-10-22T09:46:49 | {} | CONTRIBUTOR |
vuejs | core | 711,438,393 | 2,411 | sun-pandey | > try this?
>
> ```js
> watch(
> toRef(dataObject, 'propA'),
> ...
> )
> ```
propA is dynamic. Unknown until runtime. | 2020-10-18T23:14:11 | 2020-10-18T23:14:11 | {} | NONE |
vuejs | core | 711,641,638 | 2,421 | LinusBorg | > Now it does not change, it return proxy object, when in vue 2 it returned dom element
In Vue 2, it gives you the component instance, not an element - because you put the ref on a component, not a DOM element.
In Vue 3, it also does - it's just wrapped in a proxy.
It just seems that this `<LMarker>`component... | 2020-10-19T06:24:16 | 2020-10-19T06:24:16 | {} | MEMBER |
vuejs | core | 711,643,156 | 2,422 | LinusBorg | We can't understand the problem you without a reproduction. Also this is not the route repository. | 2020-10-19T06:25:43 | 2020-10-19T06:25:43 | {} | MEMBER |
vuejs | core | 712,061,762 | 2,429 | posva | 
Huh?
Edit: Forced updated the vue version and it doesn't work :+1: | 2020-10-19T11:05:29 | 2020-10-19T11:10:07 | {} | MEMBER |
vuejs | core | 710,096,093 | 2,396 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 39.97 KB (0%) |
| runtime-dom.global.prod.js | 26.3 KB (0%) |
| size-check.global.prod.js | 15.8 KB (0%) | | 2020-10-16T14:54:42 | 2020-10-19T12:08:52 | {} | NONE |
vuejs | core | 712,642,568 | 2,444 | unbyte | the component was not unmounted at all
`<my-test v-for="id in [block.id]" :key="id" />` => `<my-test v-for="b in block" :key="b.id" />` | 2020-10-20T07:07:33 | 2020-10-20T07:07:33 | {} | CONTRIBUTOR |
vuejs | core | 712,908,131 | 2,445 | HcySunYang | Consider this: https://codepen.io/hcysunyang/pen/LYZRWXp?editors=1111 | 2020-10-20T14:48:20 | 2020-10-20T14:48:20 | {
"+1": 1
} | MEMBER |
vuejs | core | 712,986,063 | 2,340 | yyx990803 | It's the correct idea, but we should be handling that inside Suspense itself. See 0227b4a6 | 2020-10-20T16:28:39 | 2020-10-20T16:28:39 | {} | MEMBER |
vuejs | core | 712,441,666 | 2,429 | LinusBorg | If we make the changes i mentioned, docs could stay as they are. Pascal-Case recommended, but camel case works as well. | 2020-10-19T21:05:25 | 2020-10-19T21:05:25 | {} | MEMBER |
vuejs | core | 712,624,098 | 2,437 | LinusBorg | Got it. | 2020-10-20T06:25:47 | 2020-10-20T06:25:47 | {} | MEMBER |
vuejs | core | 712,661,300 | 2,440 | murongg | > Another solution:
>
> ```
> <div v-lazy="{ src: errorlazy.src }" />
> ```
Can only do this, thank you | 2020-10-20T07:44:08 | 2020-10-20T07:44:08 | {} | NONE |
vuejs | core | 713,341,007 | 2,451 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-21T06:30:19 | 2020-10-21T06:30:19 | {} | NONE |
vuejs | core | 711,705,936 | 2,423 | posva | Your reproduction doesn't show the problem you are describing: the slot renders correctly. If you are bundling your own Vue components, make sure you mark Vue as an external dependency.
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2020-10-19T06:58:56 | 2020-10-19T06:59:07 | {} | MEMBER |
vuejs | core | 712,062,578 | 2,432 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 39.97 KB (-0.04% 🔽) |
| runtime-dom.global.prod.js | 26.3 KB (0%) |
| size-check.global.prod.js | 15.8 KB (0%) | | 2020-10-19T11:05:59 | 2020-10-19T12:29:08 | {} | NONE |
vuejs | core | 712,241,830 | 2,429 | Wizard67 | I'm having the same problem. | 2020-10-19T15:22:51 | 2020-10-19T15:22:51 | {} | NONE |
vuejs | core | 712,540,084 | 2,438 | haoqunjiang | 不要用 TSLint。已经 deprecate 了，下个版本的 CLI 里会去掉这个选项。 | 2020-10-20T02:01:01 | 2020-10-20T02:01:01 | {} | MEMBER |
vuejs | core | 714,309,871 | 2,456 | Jokcy | > Do this:
>
> ```js
> watchEffect(() => ..., { flush: 'post' })
> ```
Yeah, I know, but the implemention is confusing so it still need to talk if this is as expected or not. | 2020-10-22T08:01:49 | 2020-10-22T08:01:49 | {} | CONTRIBUTOR |
vuejs | core | 712,710,086 | 2,399 | unbyte | Vue can't work normally with `{ mode: 'closed' }`, even if supports mounting on shadowroot | 2020-10-20T09:10:50 | 2020-10-20T09:10:50 | {} | CONTRIBUTOR |
vuejs | core | 713,341,556 | 2,453 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-21T06:31:24 | 2020-10-21T06:31:24 | {} | NONE |
vuejs | core | 713,366,258 | 2,429 | posva | yes, it's working | 2020-10-21T07:22:20 | 2020-10-21T07:22:20 | {} | MEMBER |
vuejs | core | 713,378,180 | 2,429 | LinusBorg | https://jsfiddle.net/Linusborg/oqzhp2c7/1/
yep. | 2020-10-21T07:45:59 | 2020-10-21T07:45:59 | {} | MEMBER |
vuejs | core | 714,551,794 | 2,460 | LinusBorg | Hm ... right now we lowercase event names. However we can't easily stop doing that, as for normal events, we have to lowercase at least the first character: `'onClick' -> 'click'`, so for your event the best we could do easily is `'onMDCTab:interacted' -> mDCTab:interacted`, which would also not work.
We would have... | 2020-10-22T14:55:31 | 2020-10-22T14:57:20 | {
"confused": 2
} | MEMBER |
vuejs | core | 712,298,009 | 2,429 | LinusBorg | Since #2278 now all events are camelCased, we now have to camelCase events everywhere, mainly in two places:
1. when setting `emitsOptions` on the internal instanc
2. during the call of `emit()`, the first argument.
/cc @yyx990803 this is a pretty broad regression from `3.0.0` and might need a hotfix release. | 2020-10-19T16:55:00 | 2020-10-19T16:55:54 | {} | MEMBER |
vuejs | core | 712,870,986 | 906 | gregg-cbs | Thanks @posva !
This docs thing is a tough one isnt it. I'm finding it very difficult to find information.
Google doesn't show any pages from [https://next.router.vuejs.org/ ](https://next.router.vuejs.org/) when you google Vue 3 Router questions.
Even v3.vuejs.org is not coming up in any of my searches.
But... | 2020-10-20T13:57:16 | 2020-10-20T13:59:10 | {} | NONE |
vuejs | core | 713,044,271 | 2,449 | LinusBorg | You're using `watch` "wrong" in `watch2`, or rather: not in a way that is analogous to watch1.
See this fiddle for what the real analogous implementation looks like:
https://jsfiddle.net/Linusborg/gxv1kabs/1/
...and it behaves the same as watch1 - it doesn't log anything because `newNames === oldNames` (it's s... | 2020-10-20T18:12:02 | 2020-10-20T18:13:29 | {
"+1": 1
} | MEMBER |
vuejs | core | 713,235,514 | 2,424 | logaretm | That would be a breaking change for some, wouldn't it? I did depend on this behavior in some cases. | 2020-10-21T01:34:22 | 2020-10-21T01:34:22 | {} | NONE |
vuejs | core | 713,346,348 | 2,431 | Sunyuja | I've realized also `inline v-if/v-else` is not work a migrated code from Vue2 in Vue3.
```html
<div>
<div v-if="1">ccc</div> <div v-else>ddd</div>
</div>
```
Then I get,
```
[Vue warn]: Template compilation error: v-else/v-else-if has no adjacent v-if.
13 |
14 | <div>
15 | <div v-if="1">ccc</div... | 2020-10-21T06:41:51 | 2020-10-21T06:43:25 | {} | NONE |
vuejs | core | 713,875,027 | 2,381 | tim-janik | While I don't have a miniscule repro yet, I did figure out what the bug is.
Please add the following assertion to vue.js and then try out some non-trivial apps that use $watch, in particular call ` this.$watch` (implemented by `function instanceWatch`) with an instance that is *not* `currentInstance`:
~~~js
--- ... | 2020-10-21T21:01:16 | 2020-10-21T21:01:16 | {} | NONE |
vuejs | core | 711,650,203 | 2,423 | LinusBorg | @Alanscut Vue 3.0 doesn't support IE yet. | 2020-10-19T06:29:33 | 2020-10-19T06:29:33 | {} | MEMBER |
vuejs | core | 712,129,777 | 2,423 | bkinnamon | I appreciate all of you taking a look at this issue. I'm using Chrome 86.0.4240.80 on macOS 10.15.7. I had tried:
- restarting my computer
- removing the `node_modules` folder and `package-lock.json` and reinstalling
- building that smaller example project from scratch with the Vue CLI
Nothing would work. I rem... | 2020-10-19T12:41:50 | 2020-10-19T12:41:50 | {} | NONE |
vuejs | core | 712,451,346 | 2,431 | nfplee | Looks like the same problem I’m having. https://stackoverflow.com/questions/64432182/vue-3-removes-white-space-between-inline-block-elements.
This is a breaking change from version 2 that I haven’t seen documented. I also agree it shouldn’t change what the user intended (raw HTML). There’s other solutions to this pr... | 2020-10-19T21:25:09 | 2020-10-19T21:34:12 | {
"+1": 2
} | NONE |
vuejs | core | 714,253,227 | 2,429 | yaquawa | Thanks guys, I don't know why, but it works now automatically... | 2020-10-22T06:07:35 | 2020-10-22T06:07:35 | {} | NONE |
vuejs | core | 711,939,721 | 2,427 | javie5 | I want to know why please | 2020-10-19T09:42:12 | 2020-10-19T09:42:12 | {} | NONE |
vuejs | core | 712,295,547 | 2,437 | LinusBorg | > I think the actual issue here is that Transition is a functional HOC which doesn't even have a public instance proxy. Or more generally, any presence of a functional component in the parent chain would prevent the child from traversing all the way to the root via $parent.
I'm not sure that's exactly the issue here... | 2020-10-19T16:50:36 | 2020-10-19T16:53:16 | {} | MEMBER |
vuejs | core | 712,640,804 | 2,444 | posva | In your repro `block.id` is always undefined since `block` is an array. What I found is an error when using:
```js
const MyTest = {
template: "#my-test",
setup() {
Vue.onBeforeUnmount(() => {
console.log("MyTest umounted")
});
}
}
const App = {
components: {
MyTest
},
... | 2020-10-20T07:04:05 | 2020-10-20T07:04:05 | {} | MEMBER |
vuejs | core | 712,659,129 | 2,440 | murongg | > The component doesn't re-render because the only reactive dependency of the template - `errorlazy` did not change. `errorlazy.src` did change, but that property is not a dependency of the component.
>
> So neither the component's nor the directive's `updated()` hook runs, and that's expected.
>
> you can howeve... | 2020-10-20T07:40:07 | 2020-10-20T07:40:07 | {} | NONE |
vuejs | core | 714,302,136 | 2,456 | HcySunYang | Do this:
```js
watchEffect(() => ..., { flush: 'post' })
``` | 2020-10-22T07:47:54 | 2020-10-22T07:47:54 | {} | MEMBER |
vuejs | core | 745,089,717 | 2,821 | luwuer | Don't need to have the same filename, just make sure that the parent and child components keep the same component name.
https://codesandbox.io/s/vue3-issue2821-q0o03 | 2020-12-15T06:44:25 | 2020-12-15T06:44:58 | {} | CONTRIBUTOR |
vuejs | core | 745,113,180 | 1,641 | ItsRyanWu | > You don't. Exposing imperative methods on the component instance is not recommended. Use a prop to let other component control it.
Hey what if I want to manipulate a reactive value in 'setup' closure?
e.g.
```
setup() {
const a = ref(true)
function resetA() {
a.value = false
}
... | 2020-12-15T07:39:42 | 2020-12-15T07:46:33 | {} | NONE |
vuejs | core | 745,740,808 | 2,828 | luwuer | Your `beforeUpdate` and `updated` hooks is bind to `test-component`， your code generate a tree like this `test-component>Transition>BaseTransition`.
Update is less granular，it just update `BaseTransition`.
I am not sure if it is expected behavior.
---
I thought again, there has no workaround about this scen... | 2020-12-16T03:30:23 | 2020-12-16T03:33:24 | {} | CONTRIBUTOR |
vuejs | core | 747,825,716 | 2,791 | luwuer | > I see. I think add a hook beforeExtend which run once for each component would really help. There has been many thing indirect and inefficient for plugins via beforeCreate.
Add a lifecycle hook `beforeExtend` seems like not a recommendable resolve:
1. User have to modify code because its inconsistent with vue2
2... | 2020-12-18T02:24:12 | 2020-12-18T02:30:11 | {} | CONTRIBUTOR |
vuejs | core | 747,920,884 | 2,840 | luwuer | I see your point, can use `setAttribute('form', ...)` set `attributes` and `attributes.form` can control `form` attribute, sorry for it. | 2020-12-18T07:30:27 | 2020-12-18T07:30:27 | {} | CONTRIBUTOR |
vuejs | core | 745,458,755 | 2,819 | lukaskoeller | What is causing the error:
#### ✅ Works fine
```js
export default defineComponent({
name: 'TestButton',
```
### 🚫 Causing above described error
```js
export default defineComponent({
name: 'Button',
``` | 2020-12-15T17:52:45 | 2020-12-15T17:53:04 | {
"heart": 1
} | NONE |
vuejs | core | 745,805,800 | 2,828 | 07akioni | > Your `beforeUpdate` and `updated` hooks is bind to `test-component`， your code generate a tree like this `test-component>Transition>BaseTransition`.
>
> Update is less granular，it just update `BaseTransition`.
>
> I am not sure if it is expected behavior.
>
> I thought again, there has no workaround about th... | 2020-12-16T06:52:30 | 2020-12-16T06:52:30 | {} | CONTRIBUTOR |
vuejs | core | 745,841,046 | 2,828 | luwuer | Make lots of sense.
@fomalhaut79 if you want to do something in `beforeUpdate/updated` hooks, you can wrap like `Transition > CustomeComponent > code` , and move hooks callbacks to `CustomeComponent `. | 2020-12-16T07:39:07 | 2020-12-16T07:39:07 | {} | CONTRIBUTOR |
vuejs | core | 746,192,775 | 2,833 | LinusBorg | There's an RFC being discussed to allow for a broader solution, i.e. for computeds:
https://github.com/vuejs/rfcs/pull/212
Please give feedback there. | 2020-12-16T12:10:15 | 2020-12-16T12:10:15 | {} | MEMBER |
vuejs | core | 746,367,697 | 2,768 | edison1105 | @07akioni
I debuged this and found the reason.caused by af9560455d9719a4c5f0d6588d04bfb4c06c8654
I opened a PR,maybe close #2829 too.
I don’t have time to test #2829,I need to sleep 😄 | 2020-12-16T14:22:51 | 2020-12-16T14:47:37 | {
"+1": 4,
"laugh": 1
} | MEMBER |
vuejs | core | 747,242,308 | 2,838 | dreamSeekerYu | ready
------------------ 原始邮件 ------------------
发件人: "vuejs/vue-next" <notifications@gith... | 2020-12-17T06:35:51 | 2020-12-17T06:35:51 | {} | NONE |
vuejs | core | 747,479,802 | 1,324 | pikax | Yes `UnwrapRef<T>` can and it will be different than `T`
As you can see in this example:
```ts
const a = reactive({
b: ref(1),
c: {
ca: 1,
cb: ref('11'),
value: 2
}
})
// it will return UnwrapRef<T>
/*
{
b: 1,
c: {
ca: 1,
cb: '11',
value: 2
}
}
*/
... | 2020-12-17T14:43:16 | 2020-12-17T14:43:16 | {} | MEMBER |
vuejs | core | 747,903,219 | 2,843 | lijingfaatcumt | > IMO, this will make `shallowProxy` and `reactiveProxy` confused. Developers do not know how to choose which API to use.
I do not think so, because i think 'shallow' can show the difference, i think we should use 4 weakMap (reactiveMap, shallowReactiveMap, readolyMap, shallowReadonlyMap) to store the map relationsh... | 2020-12-18T06:45:22 | 2020-12-18T06:45:22 | {} | NONE |
vuejs | core | 747,969,250 | 2,843 | LinusBorg | We collect all reactive instances in one WeakMap, that ignores what type of `reactive` they are:
https://github.com/vuejs/vue-next/blob/b81d279e40c3d32a3740ea20d7e182690294f117/packages/reactivity/src/reactive.ts#L22-L30
This likely affects `readonly ` vs. `shallowReadonly` as well. Meaning we would in fact need ... | 2020-12-18T09:26:05 | 2020-12-18T09:28:34 | {} | MEMBER |
vuejs | core | 747,980,866 | 2,843 | lijingfaatcumt |
> We collect all reactive instances in one WeakMap, that ignores what type of `reactive` they are:
>
> https://github.com/vuejs/vue-next/blob/b81d279e40c3d32a3740ea20d7e182690294f117/packages/reactivity/src/reactive.ts#L22-L30
>
> This likely affects `readonly ` vs. `shallowReadonly` as well. Meaning we w... | 2020-12-18T09:39:52 | 2020-12-18T09:39:52 | {} | NONE |
vuejs | core | 748,013,969 | 2,846 | LinusBorg | tracked in #2843 | 2020-12-18T10:39:17 | 2020-12-18T10:39:17 | {} | MEMBER |
vuejs | core | 748,504,741 | 2,843 | LinusBorg | PR submitted, happy to get reviews. | 2020-12-19T17:55:33 | 2020-12-19T17:55:33 | {} | MEMBER |
vuejs | core | 745,227,391 | 2,817 | luwuer | Now just the following situation will prevent reusing @posva
1. pre-node has ref
&&
2. next-node ref not equal pre-node ref | 2020-12-15T11:23:56 | 2020-12-15T11:24:40 | {} | CONTRIBUTOR |
vuejs | core | 745,277,705 | 2,791 | MiniGod | The example was a simplification, so it's not that simple. I encountered this bug when upgrading from Vue 2 where this used to work.
In our app we have a global mixin that looks at another $options to generate computed properties.
Something like:
```js
const mixin = {
beforeCreate() {
const magicOptio... | 2020-12-15T13:11:20 | 2020-12-15T13:11:49 | {} | NONE |
vuejs | core | 745,712,566 | 2,821 | luwuer | Maybe we need to talk about how to adjust recursively self-reference mechanism to avoid misunderstanding, i would like to create a new issue for it.
| 2020-12-16T01:56:42 | 2020-12-16T01:56:42 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 746,074,579 | 1,600 | abalashov | Painful. This has really broken an application I attempted to upgrade to Vue 3. | 2020-12-16T10:42:19 | 2020-12-16T10:42:19 | {} | NONE |
vuejs | core | 746,144,243 | 1,600 | martinbean | @abalashov Yup. This makes Vue 3 completely unusable for me. | 2020-12-16T11:29:54 | 2020-12-16T11:29:54 | {} | NONE |
vuejs | core | 747,942,149 | 2,845 | posva | This should be oppened (or searched for in existing issues) in Vetur, or vue dx repositories (VSCode plugins) | 2020-12-18T08:23:22 | 2020-12-18T08:23:22 | {} | MEMBER |
vuejs | core | 745,118,536 | 2,246 | calvin-cg | I ran into a kind of similar problem, I posted my question in Vue Forum [here](https://forum.vuejs.org/t/scoped-style-get-a-mismatch-hash/108548).
Is my approach is wrong or it is a bug? | 2020-12-15T07:53:09 | 2020-12-15T07:53:09 | {} | NONE |
vuejs | core | 745,132,213 | 1,865 | ydsuper | **THANK YOU** VERY MUCH **!!!** | 2020-12-15T08:23:22 | 2020-12-15T08:23:22 | {
"+1": 1
} | NONE |
vuejs | core | 745,802,039 | 2,831 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-16T06:43:29 | 2020-12-16T06:43:29 | {} | NONE |
vuejs | core | 747,405,871 | 2,791 | luwuer | @edison1105 I think your solution is not completely，take a look about this #2839 | 2020-12-17T12:19:20 | 2020-12-17T12:19:54 | {} | CONTRIBUTOR |
vuejs | core | 747,503,708 | 2,469 | LinusBorg | Sounds good. Thanks for the quick feedback! | 2020-12-17T15:20:11 | 2020-12-17T15:20:11 | {} | MEMBER |
vuejs | core | 747,598,495 | 2,835 | Pashkella | > ```postcss
> .main-menu, :slotted(.main-menu) {
> ```
>
> This will apply styles to both the current component and the slotted elements.
>
> I would not recommend `:deep()` as that will apply the styles to _all_ nested DOM elements, possibly messing with styles in other, nested components. `:deep-()` is an es... | 2020-12-17T17:53:38 | 2020-12-17T17:59:46 | {} | NONE |
vuejs | core | 745,144,729 | 2,821 | posva | You need to name them differently. Using a component in its own template allows for recursive components | 2020-12-15T08:49:24 | 2020-12-15T08:49:24 | {
"+1": 1
} | MEMBER |
vuejs | core | 746,022,465 | 2,829 | edison1105 | It's really complicated too.like #2768 | 2020-12-16T10:04:59 | 2020-12-16T10:04:59 | {} | MEMBER |
vuejs | core | 746,185,821 | 1,600 | nfplee | @abalashov and @martinbean I agree, Vue 3 is unusable without this fix. | 2020-12-16T12:04:38 | 2020-12-16T12:04:38 | {} | NONE |
vuejs | core | 746,537,066 | 2,829 | luwuer | Same as #2768, like @edison1105 said, it caused by [af95604](https://github.com/vuejs/vue-next/commit/af9560455d9719a4c5f0d6588d04bfb4c06c8654) . | 2020-12-16T16:02:26 | 2020-12-16T16:02:26 | {} | CONTRIBUTOR |
vuejs | core | 747,435,724 | 1,324 | LinusBorg | @pikax Can we close this? I think the consensus is that this can't be made to work as `UnwrapRef<T>` can indeed, by design, return an interface that is not compatible with `T`? | 2020-12-17T13:22:02 | 2020-12-17T13:22:02 | {} | MEMBER |
vuejs | core | 747,815,590 | 2,791 | LongTengDao | > The example was a simplification, so it's not that simple.
I see. I think add a hook `beforeExtend` which run once for each component would really help. There has been many thing indirect and inefficient for plugins via `beforeCreate`.
| 2020-12-18T01:49:35 | 2020-12-18T01:55:33 | {} | CONTRIBUTOR |
vuejs | core | 745,212,693 | 2,817 | luwuer | Nope, you can see that all the tests is passed without change, this shows that the basic resue logic has not been breaked.
It prevents reuse(`type` and `key` are same) only when the pre-vnode has `ref`. Reusing when pre-vnode has `ref` porp will cause `ref` to hold pre/wrong value in a tick, and reset to next/right... | 2020-12-15T10:54:57 | 2020-12-15T10:54:57 | {} | CONTRIBUTOR |
vuejs | core | 747,429,156 | 2,469 | LinusBorg | Is this still an issue? The repo link doesn't work anymore. | 2020-12-17T13:09:11 | 2020-12-17T13:09:11 | {} | MEMBER |
vuejs | core | 747,504,961 | 2,840 | LinusBorg | Yep. That would mean Vue will always set it as an attribute, and setting the attribute value as `null` or `undefined` will successfully remove it, judging from my (preliminary) tests in the browser console.
We could in turn add a check for the element's type, as that attribute only exists on form elements. | 2020-12-17T15:22:04 | 2020-12-17T15:22:24 | {
"+1": 1
} | MEMBER |
vuejs | core | 747,941,827 | 2,844 | posva | Please, next time consider using the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js) for questions first. But feel free to come back and open an issue if it turns out to be a bug 🙂 | 2020-12-18T08:22:32 | 2020-12-18T08:22:32 | {} | MEMBER |
vuejs | core | 745,450,537 | 2,819 | lukaskoeller | @posva you are totally right. I tried to replicate it in JSfiddle, but I couldn't. It is working there (https://jsfiddle.net/au6ot9yh/).
Nonetheless, the above described component `<Button>` is still showing the Error. I have another component `<BottomButton>`, with only negligible differences, that also doesn't show ... | 2020-12-15T17:39:36 | 2020-12-15T17:39:36 | {} | NONE |
vuejs | core | 745,461,483 | 2,819 | lukaskoeller | Couldn't replicate the problem in a new vue-cli project. Really weird! | 2020-12-15T17:57:35 | 2020-12-15T17:57:35 | {} | NONE |
vuejs | core | 745,634,474 | 2,826 | ddosanjh | Why do you say vue is bundled into foo-test? The rollup output is only 765 bytes and contains only the code for the FooTest component.
Just to be safe however, I moved vue to devDepdency, but get same output upon bundling with rollup. Repro steps hold.
I have tried numerous rollup configurations and no matter wha... | 2020-12-15T23:37:02 | 2020-12-15T23:37:52 | {} | NONE |
vuejs | core | 745,812,011 | 2,828 | luwuer | > Not only transition, any component has <slot /> may cause the behavior.
Thank you and i found that too, so it seems a expected behavior because vue update granularity is components.
But there is no good reason for explaining the difference between Vue2 and Vue3. | 2020-12-16T07:06:56 | 2020-12-16T07:06:56 | {} | CONTRIBUTOR |
vuejs | core | 745,814,131 | 2,828 | 07akioni | > > Not only transition, any component has may cause the behavior.
>
> Thank you and i found that too, so it seems a expected behavior because vue update granularity is components.
>
> But there is no good reason for explaining the difference between Vue2 and Vue3.
Try to explain:
In vue2, the slot content... | 2020-12-16T07:11:49 | 2020-12-16T07:15:01 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 745,960,904 | 2,826 | LinusBorg | Okay, had another look.
I had the root of the problem is correct: There are two versions of Vue in bar-app. However, that doesn't happen because of it being bundled in foo-test, as I previously stated.
I happens because you import the bundled output from the other git repo locally, and when importing the componen... | 2020-12-16T09:10:23 | 2020-12-16T09:13:20 | {} | MEMBER |
vuejs | core | 746,822,755 | 2,826 | ddosanjh | Thanks for your investigation. For me, the workaround is to simply specify the NPM dependency as a git repository instead of local file-system reference. It is convenient having it as a local package when updating the code a lot, but not worth any hackery.
Hopefully anyone encountering the same issue will search for... | 2020-12-16T18:53:33 | 2020-12-16T18:53:33 | {} | NONE |
vuejs | core | 747,424,101 | 1,135 | LinusBorg | The latter doesn't seem intended to me, rather like a bug. | 2020-12-17T12:58:55 | 2020-12-17T12:58:55 | {
"heart": 1
} | MEMBER |
vuejs | core | 747,629,534 | 2,835 | Pashkella | Okay, thanks. But what about the first question? `:slotted()` pseudo element doesn't support nesting if I add it to the parent (in my example this is `.main-menu`)? | 2020-12-17T18:51:25 | 2020-12-17T18:51:25 | {
"+1": 1
} | NONE |
vuejs | core | 747,675,965 | 2,429 | LinusBorg | Please open a new issue. This will get drowned out. | 2020-12-17T20:14:43 | 2020-12-17T20:14:43 | {
"+1": 1
} | MEMBER |
vuejs | core | 747,805,518 | 2,840 | luwuer | The warning is because the form attr is readonly in button https://html.spec.whatwg.org/multipage/form-elements.html#the-button-element , i think this warning message should show to users .
Same as #2766 . | 2020-12-18T01:16:09 | 2020-12-18T01:16:53 | {} | CONTRIBUTOR |
vuejs | core | 747,903,641 | 2,840 | LinusBorg | The warning should not show, it should not happen in the first place as we should set the value via `setAttribute('form', ...)` (which is *not* readonly*) | 2020-12-18T06:46:26 | 2020-12-18T06:46:26 | {} | MEMBER |
vuejs | core | 747,944,754 | 2,843 | posva | I think that changing the order of creation of `shallowReactive` and `reactive` shouldn't change the outcome of this: https://jsfiddle.net/u8ga1pcb/ | 2020-12-18T08:30:15 | 2020-12-18T08:30:15 | {} | MEMBER |
vuejs | core | 747,985,879 | 2,843 | lijingfaatcumt | > > We collect all reactive instances in one WeakMap, that ignores what type of `reactive` they are:
> > https://github.com/vuejs/vue-next/blob/b81d279e40c3d32a3740ea20d7e182690294f117/packages/reactivity/src/reactive.ts#L22-L30
> >
> > This likely affects `readonly ` vs. `shallowReadonly` as well. Meaning we would... | 2020-12-18T09:44:15 | 2020-12-18T09:49:15 | {} | NONE |
vuejs | core | 748,013,860 | 2,843 | LinusBorg | > i have the origin object, first i reactive origin and get reactive, second i shallowReactive the origin, but i get the reactive, can not get the shallowReactive, and i do not know the result is the reactive, this is confused,because of this, cause the bug
yes. This is why we marked it as a bug.
I will close you... | 2020-12-18T10:39:02 | 2020-12-18T10:39:02 | {} | MEMBER |
vuejs | core | 743,156,140 | 2,779 | edison1105 | Maybe it's not a Vue bug, so I closed my PR.
as a workround, edit babel.config.js like this:
```javascript
module.exports = {
presets: [
'@vue/cli-plugin-babel/preset'
],
plugins: [
/* eslint-disable-next-line global-require */
[require('@vue/babel-plugin-jsx'), { isCustomElement: tag => /^io... | 2020-12-11T12:06:23 | 2020-12-15T12:27:03 | {} | MEMBER |
vuejs | core | 745,392,251 | 2,821 | fredrivett | Strange timing, but I bumped into a very similar issue yesterday, and have spent the past day trying to reduce my code down to isolate the issue.
The main difference with my issue is that I'm `name`ing the component differently in the two different components, which I thought would get around the recursion issue. An... | 2020-12-15T16:08:56 | 2020-12-15T16:20:00 | {} | NONE |
vuejs | core | 745,843,844 | 25 | 381510688 | in vue2
```
<Child @hook:mounted="doSomething"></Child>
```
parent components can listen to its children's’ lifecycle hooks. especially for third-party components.
What should we do in VUE3? | 2020-12-16T07:41:23 | 2020-12-16T07:41:23 | {} | NONE |
vuejs | core | 746,871,385 | 1,600 | abalashov | @martinbean Agreed. I don't mean to be insolent or seem entitled - it's open-source - but it's completely broken a UIkit-styled application. All the buttons are smashed together, as are some other kinds of UI widgets. If it were a question of changed defaults, I could change the behaviour, but if there's no support for... | 2020-12-16T19:22:59 | 2020-12-16T19:22:59 | {
"+1": 2,
"heart": 1
} | NONE |
vuejs | core | 747,234,294 | 2,838 | Justineo | Please remove unnecessary third party components and make your reproduction as *minimal* as possible. | 2020-12-17T06:17:05 | 2020-12-17T06:17:05 | {} | MEMBER |
vuejs | core | 747,922,443 | 2,844 | luwuer | > Component provided template option but runtime compilation is not supported in this build of Vue. Configure your bundler to alias "vue" to "vue/dist/vue.esm-bundler.js".
You are using runtime-vue and it has no compiler, so:
1. using "vue/dist/vue.esm-bundler.js" or
2. using render function | 2020-12-18T07:35:10 | 2020-12-18T07:35:10 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 748,456,570 | 2,850 | posva | Agree with @LinusBorg on creating a computed inside of a computed, makes no sense. The resulting behavior makes sense, as the computed ends up returning a computed itself.
However, you are very close to the desired solution, here is (what looks like) what you want: https://jsfiddle.net/tqauc50w/ | 2020-12-19T10:46:57 | 2020-12-19T10:46:57 | {
"+1": 1
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.