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 | 1,069,203,294 | 5,579 | Gagydzer | Thank you for your explanation.
I rewrote test 2 according to [official documentation](https://vuejs.org/guide/extras/render-function.html#rendering-slots).
Those 2 examples are equivalent (according to docs), but the case with a render function still makes the child component re-render. Bug?
`<InnerChild>
... | 2022-03-16T14:40:42 | 2022-03-16T14:40:42 | {} | NONE |
vuejs | core | 1,072,103,330 | 5,595 | LinusBorg | I'm not too sure yet wether we want apps to be implicitly unmounted when someone mounts a new app into an already use container, or we want to block, thow a warning and make developers properly and explicitly unmount themselves (see #5571). | 2022-03-18T07:36:04 | 2022-03-18T07:36:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,072,555,803 | 5,575 | a65162 | Does any maintainer want to review this PR? | 2022-03-18T16:05:21 | 2022-03-18T16:05:21 | {} | NONE |
vuejs | core | 1,065,132,253 | 5,184 | woai3c | I have the same issue:
```html
<teleport to=".component-ui-config-container">
<div></div>
</teleport>
```
But finally, I solved the problem:
```html
<teleport v-if="isLoaded" to=".component-ui-config-container">
<div></div>
</teleport>
const isLoaded = ref(false);
onMounted(() => {
i... | 2022-03-11T13:51:08 | 2022-03-11T13:52:02 | {
"+1": 1,
"heart": 1
} | NONE |
vuejs | core | 1,068,812,502 | 4,662 | lroal | Thank's, but I need to use shadow DOM. I guess another workaround would be to use global styles from the top component - instead of scoped styles in each sub component ? | 2022-03-16T07:21:13 | 2022-03-16T07:21:13 | {
"+1": 1
} | NONE |
vuejs | core | 1,069,236,462 | 5,571 | LinusBorg | @Atinux Here's what happens:
1. The second mount empties the container element.
2. But since you did not properly unmount, the previous vnode is still cached in a property of the container element
3. so the second mount's `render` finds a previous vnode, diffs against it, finds no differences to patch and thus doe... | 2022-03-16T15:13:44 | 2022-03-16T15:13:44 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,072,760,574 | 5,602 | LinusBorg | `@vue/compiler-sfc` (found here in this repo) provides options to configure this, just like it was done back then for Vue 2 in Vue CLI.
You can open an issue in Vue CLI asking for re-enabling this - though from a quick look at the latest version of vue-loader for Vue 3, I don't see how that would currently be possib... | 2022-03-18T20:06:53 | 2022-03-18T20:07:00 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,073,142,244 | 4,404 | chasegiunta | @gnuletik Am I correct in that this PR does not support named slots? If your local `apiCustomElement.ts` _does_ support named slots (please share it!), I would think it needs to be included as part of this PR, just as [vue-web-component-wrapper](https://github.com/vuejs/vue-web-component-wrapper/) supports them | 2022-03-20T01:15:57 | 2022-03-20T01:15:57 | {} | NONE |
vuejs | core | 1,065,038,897 | 5,562 | WormGirl | You are right, Thank you | 2022-03-11T11:45:35 | 2022-03-11T11:45:35 | {} | NONE |
vuejs | core | 1,065,283,616 | 5,571 | sudongyuer | I think this might be CreatApp function causes this,because when you call CreatApp function the ismounted prop will become true , but the befroe vnode and current vnode is th same,it will only update ,but when we call CreatApp this function that will cleanup innerHTML .
<img width="522" alt="image" src="https://user-... | 2022-03-11T16:37:28 | 2022-03-11T16:48:37 | {} | CONTRIBUTOR |
vuejs | core | 1,069,736,010 | 5,598 | posva | This can and is already done with a v-bind by libraries like vuetify the way you showed. If you think this new syntax is worth pursuing, you should open an RFC in the rfcs repo | 2022-03-16T23:20:10 | 2022-03-16T23:20:10 | {} | MEMBER |
vuejs | core | 1,064,882,743 | 5,570 | LinusBorg | I guess I understand the problem from google translate ... this is totally expected behavior.
* only a change of top-level properties triggers a re-render.
* but when the render happens, the whole content of `shallowObj` is used to update the DOM, so also unreactive changes (`age.bar.age`) will be part of the updat... | 2022-03-11T08:23:57 | 2022-03-11T08:23:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,065,321,651 | 5,571 | zscumt123 | I don't know if it's a bug， so I add warn | 2022-03-11T17:21:21 | 2022-03-11T17:21:21 | {} | CONTRIBUTOR |
vuejs | core | 1,065,319,173 | 5,573 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 10394176599bd5bf87cfe219db40d6c162637649
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/622b8457389edd0008d62cc2](https://app.netlify.com/sites/vuejs-coverage/deploys/622b8457389edd0008d62cc2)
😎 Browse th... | 2022-03-11T17:18:19 | 2022-03-11T17:24:03 | {} | NONE |
vuejs | core | 1,065,978,277 | 2,758 | andria-dev | Is this PR outdated? If so, it might make sense to close this if no one is working on it. If not, is there a timeline for when this fix can be merged? From my perspective, the changes to `packages/runtime-core/src/apiCreateApp.ts` look solid. | 2022-03-12T22:44:18 | 2022-03-12T22:44:18 | {} | NONE |
vuejs | core | 1,068,834,177 | 5,135 | netlify[bot] | ❌ Deploy Preview for *vuejs-coverage* failed.
🔨 Explore the source changes: 449cfccbc0bee9db13604f49abccbf28b4dc29cf
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/623197b83a850700089517fb](https://app.netlify.com/sites/vuejs-coverage/deploys/623197b83a850700089517fb)
| 2022-03-16T07:54:36 | 2022-03-16T07:56:36 | {} | NONE |
vuejs | core | 1,070,855,627 | 5,600 | leopiccionia | You're not changing the value of `state.counter`, you're just assigning the variable `state` to another `reactive` object; only the second reactive object is returned by `setup`.
For instance, if you have a watcher attached to the first `reactive`, reactivity is completely lost.
[sfc.vuejs.org](https://sfc.vuejs.... | 2022-03-17T12:21:23 | 2022-03-17T12:32:33 | {} | CONTRIBUTOR |
vuejs | core | 1,064,883,487 | 5,569 | LinusBorg | Hello ..
Thank your for your interest in this project.
However, your issue is a usage/support question, and the issue tracker is reserved exclusively for bug reports and feature requests (as outlined in our [Contributing Guide](https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md)).
We encourage you t... | 2022-03-11T08:24:55 | 2022-03-11T08:24:55 | {} | MEMBER |
vuejs | core | 1,066,467,176 | 5,581 | LinusBorg | We can't solve non-reproductible bugs that happen with 3rd party libraries (elements) sorry. | 2022-03-14T07:37:05 | 2022-03-14T07:37:05 | {} | MEMBER |
vuejs | core | 1,066,562,781 | 4,404 | martinmaillard | Any chance this will get officially supported? | 2022-03-14T09:32:16 | 2022-03-14T09:32:16 | {
"+1": 8,
"eyes": 3
} | NONE |
vuejs | core | 1,067,898,027 | 5,584 | LinusBorg | Is there a more realistic scenario in which this happens?
In your example, you use `v-model="modelValue"`, which is not allowed - you can't mutate props.
This is likely the root cause of the error: The compiler so far doesn't take this possibility into account as your can't v-model a prop directly.. | 2022-03-15T11:50:36 | 2022-03-15T11:50:36 | {
"+1": 2,
"hooray": 1
} | MEMBER |
vuejs | core | 1,068,103,793 | 4,662 | gnuletik | > Is there any solution for this in sight ? This is a big show stopper in [vitejs/vite#5731](https://github.com/vitejs/vite/issues/5731)
If you don't need to use shadow DOM, you can use your own `defineCustomElement` function from [this PR](https://github.com/vuejs/core/pull/4404) as described here: https://github.c... | 2022-03-15T15:13:02 | 2022-03-15T15:13:02 | {} | NONE |
vuejs | core | 1,068,889,667 | 5,593 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 4d3d0d61c2c26af8d69ff48089e2f2ae66911bcb
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/6231a7ae7c9dc00008fc31d7](https://app.netlify.com/sites/vue-next-template-explorer/deploys/623... | 2022-03-16T09:04:08 | 2022-03-16T09:04:49 | {} | NONE |
vuejs | core | 1,064,790,638 | 5,568 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: ad2e37931eb676f398f14cd99d795efb82f525b7
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/622ae0510da1730008121937](https://app.netlify.com/sites/vue-next-template-explorer/deploys/622... | 2022-03-11T05:38:30 | 2022-03-11T05:39:39 | {} | NONE |
vuejs | core | 1,065,805,694 | 5,571 | zscumt123 | > > I don't know if it's a bug， so I add warn
>
> Good ~ i think this is a bug.Off topic, are you Chinese? Can you add a friend to communicate with me？ vx:sudongyuer
ok | 2022-03-12T03:48:37 | 2022-03-13T12:47:51 | {} | CONTRIBUTOR |
vuejs | core | 1,067,764,341 | 5,580 | Justineo | Closing this as `v-model` is working as expected here. | 2022-03-15T09:42:55 | 2022-03-15T09:42:55 | {} | MEMBER |
vuejs | core | 1,068,447,110 | 5,584 | lidlanca | ```html
<input :value="modelValue" @input="$emit('update:modelValue', $event.target.value)"/>
``` | 2022-03-15T20:39:57 | 2022-03-15T20:39:57 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,068,925,939 | 5,593 | LinusBorg | I'm no sure that this is the right kind of solution to the issue.
While it gets rid of the quotes, it might lead to even more confusion:
```js
<script setup>
import { ref } from 'vue'
const obj = {
flag = ref(false)
}
</script>
<template>
<div v-if="obj.flag">
this should be hidden but isn't, b... | 2022-03-16T09:43:56 | 2022-03-16T09:43:56 | {} | MEMBER |
vuejs | core | 1,071,571,774 | 5,601 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: f4f8dba945df6f183cdd76f584bad7af6d04b8e0
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/6233adb2afaf540008b4ed4d](https://app.netlify.com/sites/vue-sfc-playground/deploys/6233adb2afaf540008b4ed4d)
... | 2022-03-17T21:52:54 | 2022-03-17T21:55:08 | {} | NONE |
vuejs | core | 1,067,882,717 | 5,588 | adsjim | This is actually just my browser and happens on all pages... weird, sorry. | 2022-03-15T11:30:03 | 2022-03-15T11:30:03 | {} | NONE |
vuejs | core | 1,071,571,791 | 5,601 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: f4f8dba945df6f183cdd76f584bad7af6d04b8e0
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/6233adb268e1fd0008b65186](https://app.netlify.com/sites/vue-next-template-explorer/deploys/623... | 2022-03-17T21:52:54 | 2022-03-17T21:53:40 | {} | NONE |
vuejs | core | 1,072,103,627 | 5,573 | LinusBorg | I'm not too sure yet wether we want apps to be implicitly unmounted when someone mounts a new app into an already use container (see: #5595), or we want to block, thow a warning and make developers properly and explicitly unmount themselves (this PR). | 2022-03-18T07:36:41 | 2022-03-18T07:36:41 | {} | MEMBER |
vuejs | core | 1,072,106,825 | 5,595 | jp-liu | Your consideration is right. I'm thinking about it, too. However, I think some developers will be confused if this operation leads to page blank in the development process. Maybe we should uninstall the component and give a prompt to let the developer know what he is doing, and the page will be initialized due to re mo... | 2022-03-18T07:43:03 | 2022-03-18T07:45:46 | {} | NONE |
vuejs | core | 1,073,035,106 | 4,404 | chasegiunta | Hoping to see this move along! One thing to be mindful of with this option, is how fallthrough attributes behave. For example, currently, `class` attributes are inherited on single root elements, but they also remain on the custom element leaving duplicate, nested, style declarations. This doesn't present any issues wh... | 2022-03-19T16:03:01 | 2022-03-19T17:22:53 | {
"+1": 1
} | NONE |
vuejs | core | 1,064,884,299 | 5,555 | LinusBorg | @pikax Thoughts? Am I right? Is this a limitation in TS that we can't resolve? | 2022-03-11T08:26:02 | 2022-03-11T08:26:02 | {} | MEMBER |
vuejs | core | 1,065,664,017 | 5,574 | ryanalbrecht | I agree with your statement, but I dont think a framework should be influencing my design choices. What do you think about some kind callback or event handler to interact with the instance returned from createApp()?
This is my solution
```
window.Vue = Object.create(Vue);
Vue.createApp = function(...args){
v... | 2022-03-11T23:50:32 | 2022-03-11T23:50:32 | {} | NONE |
vuejs | core | 1,068,930,800 | 5,578 | LinusBorg | the current behavior was explicitly added here:
https://github.com/vuejs/core/commit/f994b974c0a1ac95d313c8ccfc258c6ba3910b6e
So we will have to discuss if and if so, when/how we want to change this, and how people that may as of now rely on this, would be affected. | 2022-03-16T09:49:11 | 2022-03-16T09:58:26 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,072,567,697 | 5,575 | LinusBorg | as you may have noticed, we have quite a backlog of PRs, so we are thankful for your patience. | 2022-03-18T16:16:49 | 2022-03-18T16:16:49 | {} | MEMBER |
vuejs | core | 1,046,231,912 | 5,461 | posva | Same as #5460
Do [this](https://www.typescriptlang.org/play?ssl=19&ssc=1&pln=20&pc=1#code/JYWwDg9gTgLgBAbzlApgMzgXzmqERwBEAbgK4qEBQlAJigMYA2AhqnCBDaYynAOQABMigD0qZvRjBiwGAE8+iSnBUoAHpFhxgAOxgooaCbwBK6AKo6A7lGZgAQs2CMAKnLAoAzkpW-kpPVAUABEAeQBZR2c3D08ALjgAOU5eAB84AHVdGggrZT84HRTQgCMAKwTkulKyuHSqlBdSMB58lUxKDsp5DyTi8r... | 2022-02-20T12:55:28 | 2022-02-20T12:55:28 | {} | MEMBER |
vuejs | core | 1,046,372,491 | 5,464 | edison1105 | 你需要提供一个简单可复现的 demo。你的工程太复杂了，不利于排查问题。 | 2022-02-21T01:02:19 | 2022-02-21T01:02:19 | {} | MEMBER |
vuejs | core | 1,046,398,699 | 5,464 | sleeprite | 这也许是沙盒的问题，但不影响最终结果，本地拉包依旧存在这个问题 | 2022-02-21T02:02:48 | 2022-02-21T02:02:48 | {} | NONE |
vuejs | core | 1,049,433,307 | 5,357 | TechAkayy | > @TechAkayy I still think the problem is here, you try to debug
Thanks bunch for the pointer @btea , will give it a shot 👍 | 2022-02-24T02:29:17 | 2022-02-24T02:29:17 | {} | NONE |
vuejs | core | 1,050,259,910 | 5,482 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: a23438ca7bd408d1a56046a4d329f36e75d28614
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/6217f2050dc16000074ab36d](https://app.netlify.com/sites/vue-next-template-explorer/deploys/621... | 2022-02-24T21:00:57 | 2022-02-24T21:01:40 | {} | NONE |
vuejs | core | 1,046,580,177 | 5,466 | tianjunnew | > I think that's normal, with reference to[attribute-inheritance](https://vuejs.org/guide/components/attrs.html#attribute-inheritance) Can be used
>
> ```
> <script>
> export default {
> inheritAttrs: false
> }
> </script>
> <script setup>
> import Child from './Child.vue';
> </script>
> <template>
> <Ch... | 2022-02-21T08:10:52 | 2022-02-21T08:10:52 | {} | NONE |
vuejs | core | 1,047,815,304 | 5,470 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: fd6fce4dc9639f73d10a84012326ca148fa367a7
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/6214e9cd147ab00007859eaa](https://app.netlify.com/sites/vue-next-template-explorer/deploys/621... | 2022-02-22T13:49:06 | 2022-02-22T13:49:52 | {} | NONE |
vuejs | core | 1,048,300,316 | 4,686 | LogicAndTrick | It looks like support for array refs was added back in with commit 41c18effea9dd32ab899b5de3bb0513abdb52ee4, which fixes the difficulties with array refs as it's no longer necessary to use function refs for them. Closing this issue as the slot `updated` triggering is intended behaviour and there is now a good solution ... | 2022-02-22T23:13:53 | 2022-02-22T23:13:53 | {} | NONE |
vuejs | core | 1,048,310,546 | 5,469 | sqal | Is it really a bug @posva? I've never used defineComponent, but it looks to me like it's just a helper function for defining [a stateful components](https://github.com/vuejs/core/blob/9c304bfe7942a20264235865b4bb5f6e53fdee0d/packages/runtime-core/src/apiDefineComponent.ts#L189) (with type inference) and those requires ... | 2022-02-22T23:31:36 | 2022-02-22T23:31:36 | {} | CONTRIBUTOR |
vuejs | core | 1,049,211,554 | 5,472 | LinusBorg | I'm not sure we feel comfortable exposing hooks into these internals.
Can you share a bit more about the use case and what problem this solves? | 2022-02-23T21:00:26 | 2022-02-23T21:00:26 | {} | MEMBER |
vuejs | core | 1,049,492,651 | 5,473 | yaquawa | @ygj6 Got it, thanks! | 2022-02-24T04:50:16 | 2022-02-24T04:50:16 | {} | NONE |
vuejs | core | 1,049,906,713 | 5,480 | haoqunjiang | There's another potential improvement to Vue's tree-shakability:
The `sideEffects` field was removed from the main package because we don't want bundlers to shake the `registerRuntimeCompiler(compileToFunction)` call.
But we can use [array-style `sideEffects`](https://webpack.js.org/guides/tree-shaking/#mark-the-... | 2022-02-24T14:19:23 | 2022-02-24T14:19:23 | {} | MEMBER |
vuejs | core | 1,050,420,897 | 5,483 | edison1105 | 
it works fine.
| 2022-02-25T01:16:15 | 2022-02-25T01:18:28 | {} | MEMBER |
vuejs | core | 1,046,239,476 | 5,462 | Rolanddoda | @posva can you explain more about the `^` in front of the attribute trick? | 2022-02-20T13:34:43 | 2022-02-20T13:34:43 | {} | NONE |
vuejs | core | 1,046,372,789 | 5,464 | sleeprite | > 你需要提供一个简单可复现的 demo。你的工程太复杂了，不利于排查问题。
[复现地址](https://layui-vue.gitee.io/layui-vue-playground/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cCBsYW5nPVwidHNcIj5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcbmltcG9ydCB7IHNldHVwTGF5dWlWdWUgfSBmcm9tICcuL2xheXVpLXZ1ZS5qcyc7XG4vLyBzZXR1cCBmb3IgbGF5dWktdnVlLCBkb24ndCByZW1vdmUuXG5zZXR1cExheXVpVn... | 2022-02-21T01:02:53 | 2022-02-21T01:04:28 | {} | NONE |
vuejs | core | 1,049,416,517 | 5,357 | TechAkayy | > ```ts
> n1.el!.text = n2.children
> ```
Thanks @btea , firstly, thank you very much for looking into this issue. Really appreciate your help!
I applied your above suggestion, and tried again in my above reproduction, didn't really fixed it, I was wondering if you tried in the above reproduction and had any l... | 2022-02-24T01:55:44 | 2022-02-24T01:55:44 | {} | NONE |
vuejs | core | 1,049,575,684 | 1,414 | blabbath | For vite this worked for me:
```
// vite.config.js
import vue from "@vitejs/plugin-vue";
export default {
plugins: [
vue({
template: {
compilerOptions: {
isCustomElement: (tag) => tag.startsWith("cds-"),
},
},
}),
],
};
``` | 2022-02-24T07:39:18 | 2022-02-24T07:39:18 | {
"heart": 2,
"laugh": 1,
"rocket": 1
} | NONE |
vuejs | core | 1,046,406,560 | 5,465 | caozhong1996 | Nope, it's not a direct proportion that between pay and harvest, it's not worth doing😕 | 2022-02-21T02:16:46 | 2022-02-21T02:16:46 | {} | CONTRIBUTOR |
vuejs | core | 1,046,568,534 | 5,465 | LinusBorg | This 1) belongs into the vuejs/vue repo for Vue 2 and 2) would be little short of a rewrite of 50% of Vue 2. So don't expect that to happen in the foreseeable future. | 2022-02-21T07:55:16 | 2022-02-21T07:55:16 | {} | MEMBER |
vuejs | core | 1,048,372,354 | 5,469 | enpitsuLin | @sqal script-setup are excellent, but I can't use both render function and script-setup
| 2022-02-23T01:28:39 | 2022-02-23T01:28:39 | {} | NONE |
vuejs | core | 1,049,428,813 | 4,294 | Miofly | > `setup` 语法糖中的这种语法什么时候可以支持
>
> ```ts
> interface Props extends IconProps {
> value?: string;
> showAction?: boolean;
> animation?: boolean;
> actionStyle?: object;
> actionText?: string;
> }
> ```
不加?控制台还会报错，Partial 这种 ts 方法还不能用，头疼啊 | 2022-02-24T02:20:43 | 2022-02-24T02:20:43 | {
"+1": 2
} | NONE |
vuejs | core | 1,049,865,014 | 5,477 | vincerubinetti | Thank you for the information. It sounds like part of the issue is just the inconsistency of the spec itself. But yeah, if Vue is going to try to do this casing stuff "automagically", I would expect it to at least handle all the standard attributes.
---
> So you need use aria-has-popup.
This of course won't wo... | 2022-02-24T13:32:34 | 2022-02-24T13:44:23 | {} | NONE |
vuejs | core | 1,042,806,437 | 5,444 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 9a03a179e5c6019ecdac04514bd8e51b407026ef
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/621360b8a7e0730007a5e2d8](https://app.netlify.com/sites/vue-next-template-explorer/deploys/621... | 2022-02-17T10:38:14 | 2022-02-21T09:52:44 | {} | NONE |
vuejs | core | 1,046,943,023 | 5,393 | nborko | As a quick explanation of my setup, I have a subdirectory for each component with the following structure:
```ts
// types.ts
// heavily documented with tsdoc
interface MyComponentProps {
...
}
// heavily documented with tsdoc
interface MyComponentEmits {
...
}
// synthetic type for api-extrac... | 2022-02-21T14:33:56 | 2022-02-21T14:38:00 | {} | NONE |
vuejs | core | 1,047,815,319 | 5,470 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: fd6fce4dc9639f73d10a84012326ca148fa367a7
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/6214e9cd0facdd000876d43c](https://app.netlify.com/sites/vue-sfc-playground/deploys/6214e9cd0facdd000876d43c)
... | 2022-02-22T13:49:06 | 2022-02-22T13:51:36 | {} | NONE |
vuejs | core | 1,049,247,210 | 1,414 | chaderenyore | @vuesomedev What about solution for Vite.config.js | 2022-02-23T21:49:03 | 2022-02-23T21:49:03 | {} | NONE |
vuejs | core | 1,049,622,561 | 5,477 | LinusBorg | Not quite. I'd still rate this a bug.
### Why are some attributes **not hyphenated**?
Because we currently don't actively hyphenate attribute values in the patch phase. Usually that's not an issue as people normally use hyphenated attribute names in templates, but it can be an issue when i.e. passing camelCased ... | 2022-02-24T08:48:03 | 2022-02-24T08:49:12 | {
"+1": 4
} | MEMBER |
vuejs | core | 1,050,487,481 | 5,484 | xuxchao | 
| 2022-02-25T03:30:15 | 2022-02-25T03:30:15 | {} | NONE |
vuejs | core | 1,046,231,424 | 5,460 | posva | You can use the `RefUnwrapBailTypes`: https://github.com/vuejs/core/blob/main/packages/reactivity/src/ref.ts#L252-L269 to avoid unwrapping. | 2022-02-20T12:52:45 | 2022-02-20T12:52:45 | {} | MEMBER |
vuejs | core | 1,046,573,885 | 5,466 | ygj6 | I think that's normal, with reference to[attribute-inheritance](https://vuejs.org/guide/components/attrs.html#attribute-inheritance)
Can be used
```vue
<script>
export default {
inheritAttrs: false
}
</script>
<script setup>
import Child from './Child.vue';
</script>
<template>
<Child :foo="2" />
</templ... | 2022-02-21T08:03:24 | 2022-02-21T08:03:24 | {} | MEMBER |
vuejs | core | 1,046,776,441 | 5,462 | jairoblatt | @Rolanddoda `.attr` - force a binding to be set as a DOM attribute.
https://vuejs.org/api/built-in-directives.html#v-bind | 2022-02-21T11:27:03 | 2022-02-21T11:27:03 | {} | NONE |
vuejs | core | 1,048,089,913 | 5,471 | posva | The type could be `number | null` but not `number | undefined`. `undefined` is meant for non-defined values, so if you want to be able to pass undefined, you must set your prop as optional. To pass a "non-existant" value, pass `null` instead.
If you still want to have your way of handling `undefined`, you can pass a... | 2022-02-22T18:28:54 | 2022-02-22T18:28:54 | {
"-1": 1
} | MEMBER |
vuejs | core | 1,048,417,714 | 5,469 | enpitsuLin | thanks lot, I will follow #3102 and this [rfc](https://github.com/vuejs/rfcs/discussions/282) , maybe these can solve my problem | 2022-02-23T03:26:24 | 2022-02-23T03:26:24 | {} | NONE |
vuejs | core | 1,048,602,425 | 2,513 | semiaddict | FYI, I am working on a solution to allow opting out of the timestamp check.
I hope to be able to submit a pull request very soon. | 2022-02-23T09:43:44 | 2022-02-23T09:43:44 | {
"hooray": 3
} | NONE |
vuejs | core | 1,049,590,596 | 5,477 | ygj6 | In fact,The [ariaHasPopup](https://developer.mozilla.org/en-US/docs/Web/API/Element/ariaHasPopup) property of the Element interface reflects the value of the aria-haspopup attribute.So you need use `aria-has-popup`. | 2022-02-24T08:03:54 | 2022-02-24T08:03:54 | {} | MEMBER |
vuejs | core | 1,049,966,748 | 1,072 | vedantnd111 | > I'm also having this issue and I am not even using typescript.
me too,I am using vue2 ,let me know if you get anything on this issue | 2022-02-24T15:19:49 | 2022-02-24T15:19:49 | {
"+1": 2
} | NONE |
vuejs | core | 1,050,259,911 | 5,482 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: a23438ca7bd408d1a56046a4d329f36e75d28614
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/6217f2057e9a8c000729fcdd](https://app.netlify.com/sites/vuejs-coverage/deploys/6217f2057e9a8c000729fcdd)
😎 Browse th... | 2022-02-24T21:00:57 | 2022-02-24T21:06:49 | {} | NONE |
vuejs | core | 1,046,565,122 | 5,441 | LinusBorg | You seem to misunderstand the documentation. You *can* use self-closing tags in SFCs templates. You posted the example yourself.
You should not use them when defining the template directly in the DOM (with a *native* template element (as opposed to in an SFC or string), because that's not guaranteed to be supported ... | 2022-02-21T07:49:45 | 2022-02-21T08:41:11 | {} | MEMBER |
vuejs | core | 1,048,499,909 | 5,471 | livthomas | It could be `number | null` if I had control over the data that is coming in but I don't. It comes from the API and the field is either present there or not (in which case the value is `undefined`).
I don't want to put `:count="count ?? null"` everywhere just because Vue cannot handle `undefined`. I will rather make... | 2022-02-23T07:09:26 | 2022-02-23T07:13:35 | {
"+1": 2
} | NONE |
vuejs | core | 1,049,405,521 | 5,473 | yaquawa | Hi @posva @caozhong1996 I have read the doc page you provided. But I couldn't see why this is expected. What's the reason for this? | 2022-02-24T01:32:08 | 2022-02-24T01:32:08 | {} | NONE |
vuejs | core | 1,049,625,813 | 5,478 | ryanlin1986 | This is by design, you should use cmptuedRef.value, or unref(computedVal) instead,.
You may think this is weird, but automatically unref will definitely increase the overhead for template rendering. | 2022-02-24T08:51:59 | 2022-02-24T08:51:59 | {} | NONE |
vuejs | core | 1,050,259,908 | 5,482 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: a23438ca7bd408d1a56046a4d329f36e75d28614
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/6217f20571671b0008b607fe](https://app.netlify.com/sites/vue-sfc-playground/deploys/6217f20571671b0008b607fe)
... | 2022-02-24T21:00:57 | 2022-02-24T21:03:04 | {} | NONE |
vuejs | core | 1,050,402,396 | 5,371 | kuang-lingxi | @LinusBorg hi! can i ask a question about watch implementation? why do we treat ref and shallow ref differently, when we use shallow ref, the callback function is forced to fire.I don't seem to see the corresponding instructions on the official documentation.
https://github.com/vuejs/core/blob/5898629d723e82b68e9b17... | 2022-02-25T00:42:00 | 2022-02-25T00:42:00 | {} | CONTRIBUTOR |
vuejs | core | 1,046,567,750 | 5,466 | LinusBorg | We recently had an issue about this and concluded that this is the correct behavior. | 2022-02-21T07:53:55 | 2022-02-21T07:53:55 | {} | MEMBER |
vuejs | core | 1,046,583,658 | 5,466 | ygj6 | > > I think that's normal, with reference to[attribute-inheritance](https://vuejs.org/guide/components/attrs.html#attribute-inheritance) Can be used
> > ```
> > <script>
> > export default {
> > inheritAttrs: false
> > }
> > </script>
> > <script setup>
> > import Child from './Child.vue';
> > </script>
> >... | 2022-02-21T08:14:50 | 2022-02-21T08:14:50 | {} | MEMBER |
vuejs | core | 1,047,815,300 | 5,470 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: fd6fce4dc9639f73d10a84012326ca148fa367a7
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/6214e9cdf1f8300007e6eaae](https://app.netlify.com/sites/vuejs-coverage/deploys/6214e9cdf1f8300007e6eaae)
😎 Browse th... | 2022-02-22T13:49:05 | 2022-02-22T13:54:28 | {} | NONE |
vuejs | core | 1,048,523,961 | 5,469 | posva | It's not a bug, I somehow read a functional component but it's was a regular one... This is indeed expected for stateful components | 2022-02-23T07:56:26 | 2022-02-23T07:56:26 | {} | MEMBER |
vuejs | core | 1,049,213,278 | 5,467 | LinusBorg | I also took a stab at this in #5033 | 2022-02-23T21:02:42 | 2022-02-23T21:02:42 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,049,900,942 | 5,480 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 7b8b4c2f525c3ee2cf7be5349bd30fcaf366c6d2
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/6217927e5c702b0008ab705b](https://app.netlify.com/sites/vuejs-coverage/deploys/6217927e5c702b0008ab705b)
😎 Browse th... | 2022-02-24T14:13:26 | 2022-02-24T14:20:38 | {} | NONE |
vuejs | core | 1,050,413,533 | 5,371 | edison1105 | @kuang-lingxi see #2231 | 2022-02-25T01:00:43 | 2022-02-25T01:00:43 | {} | MEMBER |
vuejs | core | 1,045,981,221 | 5,458 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: f06426333c2f0a1a3524acd9906dad7e2c859700
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/62121620701b550007932086](https://app.netlify.com/sites/vuejs-coverage/deploys/62121620701b550007932086)
😎 Browse th... | 2022-02-19T09:58:12 | 2022-02-20T10:28:14 | {} | NONE |
vuejs | core | 1,046,251,685 | 5,462 | posva | Same a .attr modifier for v-bind | 2022-02-20T14:36:43 | 2022-02-20T14:36:43 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,049,087,653 | 5,475 | LinusBorg | This is normal behavior. A vnode's `props` property contains the raw props. When a component instance is created for the vnode, the raw props are processed, and part of that if to cast boolean props correctly.
We can't reliably know during compilation that the vnode will represent a component (vs. a normal element),... | 2022-02-23T18:33:14 | 2022-02-23T18:34:07 | {} | MEMBER |
vuejs | core | 1,050,488,560 | 5,481 | ygj6 | Looks like cross-references are causing the problem. comment
```vue
<script lang="ts" setup>
// import A from './A.vue';
const props = defineProps<{ count: number }>()
</script>
<template>
<!-- <A v-if="props.count > 0" :count="props.count-1" /> -->
<li>B</li>
</template>
```
Will work properl... | 2022-02-25T03:32:29 | 2022-02-25T03:32:29 | {} | MEMBER |
vuejs | core | 1,046,548,187 | 5,441 | classmatewu | I am a Vue beginner, I am more interested in this piece, thank you | 2022-02-21T07:23:27 | 2022-02-21T07:23:27 | {} | NONE |
vuejs | core | 1,048,410,011 | 5,357 | btea | I debugged a bit and the problem seems to be here
https://github.com/vuejs/core/blob/5898629d723e82b68e9b17b91bf8b1a8390a3912/packages/runtime-core/src/renderer.ts#L498-L500
I think the solution should be to update the value of `n1.el.text` before assigning it to `n2.el`, code show as below. Do you think it's fe... | 2022-02-23T03:07:19 | 2022-02-23T03:19:24 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,048,601,872 | 3,933 | semiaddict | This seems related to #2513. | 2022-02-23T09:43:01 | 2022-02-23T09:43:01 | {} | NONE |
vuejs | core | 1,049,633,374 | 5,478 | xhxhxhxh | It worked, thanks | 2022-02-24T09:01:38 | 2022-02-24T09:01:38 | {} | NONE |
vuejs | core | 1,049,900,878 | 5,480 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 7b8b4c2f525c3ee2cf7be5349bd30fcaf366c6d2
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/6217927e48fcda0009538a81](https://app.netlify.com/sites/vue-next-template-explorer/deploys/621... | 2022-02-24T14:13:23 | 2022-02-24T14:14:08 | {} | NONE |
vuejs | core | 1,050,024,635 | 4,803 | Shinigami92 | I can reproduce this, but I see there is already a PR :tada:
Is it planned to get released soon? | 2022-02-24T16:18:54 | 2022-02-24T16:18:54 | {} | CONTRIBUTOR |
vuejs | core | 1,046,378,245 | 5,464 | edison1105 | 
构建产物里并没有找到 `changeThemeVariable`。而且`lay-config-provider`中也没有相关的逻辑。🤔 | 2022-02-21T01:15:53 | 2022-02-21T01:15:53 | {} | MEMBER |
vuejs | core | 1,046,390,886 | 5,464 | edison1105 | 打开 `https://cdn.jsdelivr.net/npm/@layui/layui-vue@latest/lib/index.js`
跟打开
`https://cdn.jsdelivr.net/npm/@layui/layui-vue@0.3.8-alpha.8/lib/index.js`
看到的产物是不一样的。
@latest 中不包含切换主题的代码
@0.3.8-alpha.8 中包含切换主题的代码。
但切换版本，指向的是@latest
| 2022-02-21T01:42:09 | 2022-02-21T01:43:24 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.