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,588,124,671 | 7,683 | sxzz | I don't think these changes are necessary. Could you please provide us with more detailed information about this PR? | 2023-06-12T21:22:53 | 2023-06-12T21:22:53 | {} | MEMBER |
vuejs | core | 1,581,444,799 | 7,448 | ChuChencheng | Another similar [reproduction](https://chuchencheng.github.io/vue-memory-leak/) here with Vue 3.3.4
I've tested in private mode.
1. Switch to 'SelectPage' tab and switch back to 'EmptyPage'
2. GC
The heap size/DOM nodes did not go back.
But it worked as expected when I switched between EmptyPage and DivPage ta... | 2023-06-07T20:12:34 | 2023-06-07T20:12:34 | {} | NONE |
vuejs | core | 1,581,930,392 | 5,250 | baiwusanyu-c |
someObject: SomeObject | SomeObject[] 😂
> @baiwusanyu-c I saw a different code. [see](https://play.vuejs.org/#__DEV__eNp9kMFOwzAMhl8lygmkNTmMUynTEA8AEkfCoe3ckrE4keOOw+i7k7ajVEPaIVJsJ9/v/z/JxxDUsQOZyyLWZAOLCNwFcSixfTCSo5EbgxYZqClrEK/ewXO1h5rFyaAQovE+F5HJYrsaG1VJucDOVUAG+6GVzhLx5F14IR/imSDizEykP/73onh7H1kGd9BYhPF7M... | 2023-06-08T05:51:26 | 2023-06-08T05:51:26 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,582,313,904 | 8,519 | Justineo | React 下也有可以抽离出静态 CSS 文件的方案，Vue 组件的样式文件也可以编译成 JS 模块输出，这也不是写法习惯的问题。 | 2023-06-08T10:20:12 | 2023-06-08T10:20:12 | {} | MEMBER |
vuejs | core | 1,582,463,360 | 8,523 | baiwusanyu-c | I will add unit testing later. In addition, for judging conditions, I have to consider it again | 2023-06-08T12:05:19 | 2023-06-08T12:05:19 | {} | MEMBER |
vuejs | core | 1,582,645,256 | 8,388 | hellolex | 原来如此，我一直习惯在同一个单文件中写多个组件，开发使用vue3+webpack，啥都不用配置直接就能在文件中使用jsx，而且jsx组件和template的组件都能共同运行，开发和构建没有问题。结果这两天建了新项目同样的配置就怎么都运行不了，也是同样的报错，郁闷极了 | 2023-06-08T14:08:42 | 2023-06-08T14:08:42 | {} | NONE |
vuejs | core | 1,584,176,511 | 8,526 | baiwusanyu-c | In your demo there are typo mistakes and ref syntax errors
```
const changedTimes = ref(0)
watch(singleSetting.val, (current, previous) => {
console.log('changed', current, previous)
changedTime++;
})
``` | 2023-06-09T08:26:15 | 2023-06-09T08:26:15 | {} | MEMBER |
vuejs | core | 1,586,704,741 | 8,247 | simaotwx | See https://github.com/nuxt/nuxt/issues/20945#issuecomment-1555936037 for what solved it for me | 2023-06-12T07:01:25 | 2023-06-12T07:01:25 | {
"+1": 1
} | NONE |
vuejs | core | 1,587,143,086 | 8,543 | sxzz | No, it doesn't need to. The only thing that needs to be done is to add `typesVersions` in the package.json file of Vue.
https://www.typescriptlang.org/docs/handbook/declaration-files/publishing.html#version-selection-with-typesversions | 2023-06-12T11:29:07 | 2023-06-12T11:29:07 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,589,255,616 | 3,532 | sxzz | Closing this. Starting from Vue 3.3, we are utilizing faster types generation by transitioning from @microsoft/api-extractor to rollup-plugin-dts. | 2023-06-13T12:53:28 | 2023-06-13T12:53:28 | {} | MEMBER |
vuejs | core | 1,580,048,450 | 7,499 | Triloworld | @LinusBorg can this pull request be checked and incorporated? thx | 2023-06-07T06:59:34 | 2023-06-07T06:59:34 | {
"heart": 1
} | NONE |
vuejs | core | 1,581,935,426 | 5,250 | edison1105 | Ah, This is awkward. 😄
Thanks @baiwusanyu-c | 2023-06-08T05:58:21 | 2023-06-08T05:58:21 | {} | MEMBER |
vuejs | core | 1,582,322,043 | 8,519 | baiwusanyu-c | ````
<template>
<div :style="class1">
Hello, world!
</div>
</template>
<script setup>
const class1 = {
color: 'red',
fontSize: '20px',
}
</script >
````
为什么不这么做？ | 2023-06-08T10:24:17 | 2023-06-08T10:24:30 | {} | MEMBER |
vuejs | core | 1,582,645,981 | 8,524 | Neper98 | update volar and restart u vscode plz! | 2023-06-08T14:09:08 | 2023-06-08T14:09:08 | {
"+1": 1
} | NONE |
vuejs | core | 1,583,577,816 | 8,286 | dimatakoy | In my personal view its so painfully. We have **limited** typescript and **usual typescript** together, in one place. This feels **strange**, **unpredictable** and **boilerplaty**, since we must declare app types and **special** types for half of components.
Generating runtime checks from declarations was a bad idea... | 2023-06-08T23:12:56 | 2023-06-08T23:12:56 | {} | NONE |
vuejs | core | 1,585,612,616 | 7,593 | sxzz | /ecosystem-ci run | 2023-06-10T10:45:34 | 2023-06-10T10:45:34 | {} | MEMBER |
vuejs | core | 1,588,624,196 | 8,564 | binyet | 首先感谢您的回复，我也在Vue playground试过，结果确实如此。
但是在vsCode中运行后，打开浏览器的console却是以下结果
| 2023-06-13T06:26:03 | 2023-06-13T06:26:03 | {} | NONE |
vuejs | core | 1,582,194,856 | 8,519 | tianxiadys | Translate to English:
**What problem does this feature solve?**
The current <style scope> works well in most cases, but not in these two situations:
1. Vue components that need to be exported as third-party libraries. For React, I only need to import the JS file of the third-party library in the project, but f... | 2023-06-08T09:12:40 | 2023-06-08T09:12:40 | {} | NONE |
vuejs | core | 1,585,991,363 | 8,517 | sxzz | We have to hoist `defaultsObject` like this [Vue Playground](https://play.vuejs.org/#eNpdjjFrwzAQhf/KoSUJtDVdg2IotHO7FrSoztlRsaRDOrmD0H/vJQ4ZPL473ve+qt6IXpaC6qh0HpIjhtmG6WQUZ6N6E4YYMsMZR1tmzp8/vzgwnKBCsB6PYNTHYgN8x2IUNBN0t1KkKeFOzMiFNlznKSYWTsIRGowpetiJyO5aBFhnKUXKsvbn+PJ+V9iLiwv4dX3pulpkTi5Mrd8fnjaqh60So6fZMkoC0JfXvlb... | 2023-06-11T03:35:17 | 2023-06-11T03:35:23 | {} | MEMBER |
vuejs | core | 1,585,992,608 | 8,517 | sxzz | Maybe we can hoist the variables if they are only used in macros. | 2023-06-11T03:37:24 | 2023-06-11T03:37:24 | {} | MEMBER |
vuejs | core | 1,586,398,952 | 3,948 | sxzz | ATM, we can try the solution below. It has type validation and absent checking.
For `<script setup lang="ts">`
```ts
const props = defineProps({
msg: {
type: [Boolean, null] as PropType<boolean | null>,
required: true
}
})
// or using type declaration
const props = defineProps<{
msg: boolea... | 2023-06-12T00:29:55 | 2023-06-12T00:29:55 | {
"+1": 10,
"heart": 5,
"hooray": 2,
"rocket": 2
} | MEMBER |
vuejs | core | 1,587,298,507 | 8,553 | Alfred-Skyblue | Maybe you should use dynamic components rendering?
```vue
<Table v-slot="{ Column }">
<component :is="Column"></component>
</Table>
``` | 2023-06-12T13:01:20 | 2023-06-12T13:01:20 | {} | MEMBER |
vuejs | core | 1,588,933,085 | 8,391 | yyx990803 | `<script setup>` requires cross-script-template static analysis. The compilation of the script relies on information about the template. | 2023-06-13T09:40:11 | 2023-06-13T09:40:11 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,583,220,711 | 8,526 | panstromek | From some further testing, it looks like `v-model` will replace the whole `Ref` with a primitive `boolean` value after you press the checkbox. It seems that the root object is assumed to be reactive but it isn't in this case.
I feel like I have an intuition for why this happens, but it's a bit unfortunate footgun, c... | 2023-06-08T19:36:18 | 2023-06-08T19:39:48 | {} | NONE |
vuejs | core | 1,587,323,363 | 8,553 | Fuzzyma | @Alfred-Skyblue yes, this would work, but it gets kinda cumbersome and is very unintuitive. Usually you can just use any variable from your script section and render it as a component. Why the limitation for slotprops? The developer usually doenst know the internals and assumes that it just works "the same"
// EDIT:... | 2023-06-12T13:14:32 | 2023-06-12T13:19:38 | {
"+1": 1
} | NONE |
vuejs | core | 1,583,029,435 | 8,286 | gorankarlic | If understand correctly this issue (which I also ran into) basically means that Vue 3 only supports "trivial" TypeScript types for props.
In my opinion this in fact means that "Vue does not actually support TypeScript (but just a small subset of it)" - while the documentation misstates that it "provides first-class ... | 2023-06-08T16:57:09 | 2023-06-08T16:58:04 | {
"+1": 14
} | NONE |
vuejs | core | 1,586,007,300 | 7,890 | sxzz | The first one is resolved in #7949 | 2023-06-11T04:23:55 | 2023-06-11T04:23:55 | {} | MEMBER |
vuejs | core | 1,587,300,385 | 8,547 | edison1105 | /ecosystem-ci run | 2023-06-12T13:02:13 | 2023-06-12T13:02:13 | {} | MEMBER |
vuejs | core | 1,587,333,793 | 8,553 | jacekkarczmarczyk | it does show when i tested it in your playground | 2023-06-12T13:20:55 | 2023-06-12T13:45:34 | {} | CONTRIBUTOR |
vuejs | core | 1,588,306,092 | 4,339 | hezhongfeng | 我试着完成了一个不完善的页面堆栈管理，目前唯一的缺点是不能使用transition.
https://github.com/hezhongfeng/vue-page-stack | 2023-06-13T00:44:18 | 2023-06-13T00:44:18 | {} | NONE |
vuejs | core | 1,589,535,892 | 8,565 | Alfred-Skyblue | > I think the best approach to maintaining consistency is by implementing an ESLint rule.
I added `@typescript-eslinteslint-plugin` dependency and added ESLint rule | 2023-06-13T15:23:50 | 2023-06-13T15:23:50 | {} | MEMBER |
vuejs | core | 1,581,931,261 | 5,250 | baiwusanyu-c | > @baiwusanyu-c I saw a different code. [see](https://play.vuejs.org/#__DEV__eNp9kMFOwzAMhl8lygmkNTmMUynTEA8AEkfCoe3ckrE4keOOw+i7k7ajVEPaIVJsJ9/v/z/JxxDUsQOZyyLWZAOLCNwFcSixfTCSo5EbgxYZqClrEK/ewXO1h5rFyaAQovE+F5HJYrsaG1VJucDOVUAG+6GVzhLx5F14IR/imSDizEykP/73onh7H1kGd9BYhPF7MYM2N7f3Bgs9OUj7FgwuHEqG4a7nQq6kdcETZ64Mah89Jt/... | 2023-06-08T05:52:41 | 2023-06-08T05:52:41 | {} | MEMBER |
vuejs | core | 1,584,167,172 | 8,526 | baiwusanyu-c | ```
<template>
<div>
<div v-for="setting in settings" :key="setting.key">
<input v-model="setting.val.value" type="checkbox" >
</div>
Checkbox changed times: {{changedTimes}}
</div>
</template>
<script setup lang="ts">
import { ref, watch } from "vue";
const singleSetting = {
key:... | 2023-06-09T08:18:38 | 2023-06-09T08:22:33 | {} | MEMBER |
vuejs | core | 1,585,545,963 | 8,502 | phonty29 | nice ! | 2023-06-10T08:02:13 | 2023-06-10T08:02:13 | {} | NONE |
vuejs | core | 1,586,080,447 | 8,540 | sxzz | You should report it to Element Plus first. | 2023-06-11T08:52:56 | 2023-06-11T08:52:56 | {} | MEMBER |
vuejs | core | 1,588,613,993 | 8,564 | liulinboyi | I have a try in [TypeScript playground](https://www.typescriptlang.org/play?ts=5.0.4#code/FASwdgLgpgTgZgQwMZQAQEkDiUIAUEDm4CEIA9mALJkAmUANqgN7CpuoD0AVF6oMr6gWSVArhmAYf8BzcgEZAAPqBpzRGAuOQAMgN9NAFhGAuT0CwcoDAlIYFPzQEfRgC0VAFwmouHVuwAOhKOjB0AHgC5UYAK4BbAEawA3FZstgRQAMogAF5Qbp6+AcAAvsDASPQIAM4ZqNh4hMSkFNR0jCBe1vRQXlCQ2Vg4... | 2023-06-13T06:15:59 | 2023-06-13T06:19:39 | {} | MEMBER |
vuejs | core | 1,588,685,602 | 8,547 | Alfred-Skyblue | The error of ecoystem-ci confuses me, it seems to have nothing to do with this PR. | 2023-06-13T07:15:10 | 2023-06-13T07:15:10 | {} | MEMBER |
vuejs | core | 1,588,708,017 | 8,564 | binyet | 我按照您的方法试了一下，确实如此。非常感谢您的答复！ | 2023-06-13T07:29:25 | 2023-06-13T07:29:25 | {} | NONE |
vuejs | core | 1,370,651,903 | 7,461 | sxzz | Could you please add a unit test for the issue? | 2023-01-04T09:09:26 | 2023-01-04T09:09:26 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,091,861,171 | 5,673 | posva | @truefusion only for things that cannot be done with composition api, like the ones mentioned in docs, in other words: **that isn't mixing composition api and options api, it's adding component options** | 2022-04-07T15:11:07 | 2023-01-04T13:21:36 | {} | MEMBER |
vuejs | core | 1,375,414,239 | 7,487 | LinusBorg | ~~As I said: that's a typo.~~
Ed it: not a typo. The example in the docs uses runtime props annotations:
```ts
const props = defineProps({
disabled: Boolean
})
````
quivalent to a "normal" props definition:
```ts
defineComponent({
props: {
disabled: Boolean
}
})
```
This works fine, the I... | 2023-01-09T10:41:27 | 2023-01-09T10:50:13 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,378,352,180 | 7,501 | LinusBorg | 1. If you bundle your library with vite, all reactivity transform globals are removed. there's not $() anymore
2. If you bundle your library with vite, the consuming project does not have to activate Reactivity Transform
3. If you find that vite-plugin-vue claims to skip node_modules for reactivity Transform, but doe... | 2023-01-11T07:45:28 | 2023-01-11T07:45:50 | {} | MEMBER |
vuejs | core | 1,371,606,550 | 7,392 | edison1105 | @edikdeisling
this is because `scrollIntoView()` triggers [forces layout/reflow](https://gist.github.com/paulirish/5d52fb081b3570c81e3a) and `layout/reflow` will restart a CSS animation.
see https://www.harrytheo.com/blog/2021/02/restart-a-css-animation-with-javascript/ | 2023-01-05T00:58:19 | 2023-01-05T01:01:15 | {} | MEMBER |
vuejs | core | 1,375,348,099 | 7,484 | LinusBorg | enter-to-class is not applied continuously, only for a tick at the end. the proposed solution *is* correct. If you have CSS order issues, make the from class of higher specificity. And yes, with tailwind that means you would have to create a class with `@apply` in this specific case. In others, whe the transitioned va... | 2023-01-09T09:48:25 | 2023-01-09T09:48:25 | {} | MEMBER |
vuejs | core | 1,377,272,749 | 7,495 | posva | did you try testing out without Vue? This seems a bit too weird to be related to vue itself | 2023-01-10T13:27:49 | 2023-01-10T13:27:49 | {} | MEMBER |
vuejs | core | 1,379,769,013 | 7,510 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 64af9ffbf0277245278c8e926e86e80c014ce517 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-12T03:34:27 | 2023-01-12T03:34:27 | {} | NONE |
vuejs | core | 1,379,938,160 | 6,861 | abitwhy | A better workaround:
```css
~ :deep(h1),
:deep(h1) {
color: red;
}
``` | 2023-01-12T07:56:25 | 2023-01-12T07:56:25 | {} | NONE |
vuejs | core | 1,379,960,346 | 7,514 | sxzz | See https://github.com/johnsoncodehk/volar/issues/465#issuecomment-914592624 | 2023-01-12T08:17:53 | 2023-01-12T08:17:53 | {} | MEMBER |
vuejs | core | 1,381,035,923 | 7,300 | steveworkman | @LinusBorg thanks for the guidance, with help from @danielroe I got nuxt to set the `isCustomElement` function at runtime and confirmed that this works when combined with this patch. Please re-review | 2023-01-12T21:54:20 | 2023-01-12T21:54:20 | {} | NONE |
vuejs | core | 1,370,554,753 | 7,458 | LinusBorg | I get your point of view. Several things to consider:
First off, technically, the root object is special, it represents the component instance itself. while it's a proxy, it's not a reactive data proxy - instead the proxy's job is to provide the template access to the different properties defined in the options:
... | 2023-01-04T07:07:12 | 2023-01-04T07:07:39 | {} | MEMBER |
vuejs | core | 1,370,921,862 | 5,673 | jess-ika | same issue here with webpack, everything works fine in dev mode but not in build mode. Any ideas please ? | 2023-01-04T13:19:58 | 2023-01-04T13:19:58 | {} | NONE |
vuejs | core | 1,375,565,036 | 7,479 | LinusBorg | > Technical: you mean you can not compile the parent sfc on its own then? Because I don't see an issue for the child component, unless I'm missing something that I didn't get.
slot content is compiled into a function which is passed down to the child component. This function has a closure over the parent template, ... | 2023-01-09T12:36:51 | 2023-01-09T12:36:51 | {} | MEMBER |
vuejs | core | 1,377,835,374 | 7,497 | LinusBorg | The current behavior is pretty much intended the way it is. We considered defaults to be internal an not requiring reflection on the element.
The docs you link may not be specific enough in that regard, but refer to props being reflected eher appropriate, and in our implementation, that means "when the user sets one... | 2023-01-10T20:52:41 | 2023-01-10T20:52:41 | {} | MEMBER |
vuejs | core | 1,377,942,111 | 7,497 | SavkaTaras | Hello @LinusBorg ,
I hope you are doing well.
Thank you for such a speedy reply. We appreciate all your and your team's hard innovative work.
In my opinion props handling is correct if a user passes all the props that override the defaults.
What makes it complicated:
Imagine we have a `<custom-video>` web co... | 2023-01-10T21:54:59 | 2023-01-10T21:54:59 | {} | NONE |
vuejs | core | 1,378,879,900 | 7,048 | sxzz | It seems to be an issue with TypeScript, maybe. Bulit-in `Awaited` will break the `Raw` type.
Try this one:
```diff
+++ type Awaited<T> = T extends PromiseLike<infer U> ? U : T
export function useFoo(
options?: UseQueryOptions<Awaited<Raw<{ foo: string }>>>
) {
return useQuery({
queryKey: ['foo'],... | 2023-01-11T14:55:32 | 2023-01-11T14:55:32 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,374,198,433 | 7,478 | AlttiRi | The related question:
Why `readonly` returns such complicated type `DeepReadonly<Ref<T>>`/`Readonly<Ref<T>>`?
Why not just `DeepReadonly<T>`/`Readonly<T>`?
It would be much more convenient. | 2023-01-06T22:17:03 | 2023-01-06T22:20:14 | {} | NONE |
vuejs | core | 1,375,408,759 | 7,177 | LinusBorg | * The fact that the TS behavior is different when using `defineProps()` is the bug discussed in #7487. The inferred type should just be `boolean`, because missing boolean props are always cast to `false`, so they can't be `undefined`.
* The behavior for `{ type: Boolean }` is explained in the section I linked to (swit... | 2023-01-09T10:36:15 | 2023-01-09T10:40:11 | {} | MEMBER |
vuejs | core | 1,375,919,122 | 7,487 | AlttiRi | **Is _it_ a bug?**
~I think, it works as expected.~
You use `?` it's why you get `| undefined`.
---
Another example without any Vue.js code:
```ts
type TypeA = {
prop1?: boolean
};
const b = {} as TypeA;
const prop1: boolean | undefined = b.prop1; // OK
```
Without `?`:
```ts
type TypeB = {
... | 2023-01-09T16:35:03 | 2023-01-09T18:00:08 | {} | NONE |
vuejs | core | 1,373,615,840 | 7,476 | LinusBorg | > A checkbox cannot be set to indeterminate state by an HTML attribute - it must be set by a JavaScript.
https://www.w3schools.com/jsref/prop_checkbox_indeterminate.asp
So ab immediate workaround would be to write a custom directive for this.
We can look into wether this warrants special handling in hydration. | 2023-01-06T13:19:59 | 2023-01-10T06:53:58 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,378,315,132 | 7,497 | LinusBorg | Thanks for the explanation. However, I think your own explanation makes it clear that this is not really an issue:
the situation only applies to boolean attributes, and specifically to a case where you would use `true` as the default for its absence. I would rate this an anti-pattern. You say:
> The controls wi... | 2023-01-11T06:59:47 | 2023-01-11T06:59:47 | {} | MEMBER |
vuejs | core | 1,373,301,737 | 7,475 | baiwusanyu-c | I tried adding a unit test, but there is a difference in how the `setProperty` method handles `undefined` in `node` vs `browser`, which prevents me from reproducing #7474 in `jest`, I think I need some guidance | 2023-01-06T07:53:35 | 2023-01-06T07:53:35 | {} | MEMBER |
vuejs | core | 1,374,368,590 | 7,481 | RosApr | 
| 2023-01-07T03:52:08 | 2023-01-07T03:52:08 | {} | NONE |
vuejs | core | 1,377,488,410 | 6,812 | Akryum | This performance issue should hopefully be fixed by https://github.com/vuejs/devtools/commit/60aeed218badfed81b7e7957ebd0c0b521de4cfa | 2023-01-10T16:00:02 | 2023-01-10T16:00:09 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,378,341,814 | 7,501 | LinusBorg | From the reproduction provided in the other repo, I don't see how this is a bug. It's documented that ReactivityTransform will transform `$()` in any projects files. So if you activate this transform, don't use that function name for anything else. Specifically, likely: don't use JQuery.
You also say how it's a prob... | 2023-01-11T07:32:52 | 2023-01-11T07:33:39 | {} | MEMBER |
vuejs | core | 1,378,345,626 | 7,501 | LinusBorg | Also as a sidenote: this is an still an experimental API, subject to change. | 2023-01-11T07:37:44 | 2023-01-11T07:37:44 | {} | MEMBER |
vuejs | core | 1,378,347,741 | 7,501 | zz541843 | > From the reproduction provided in the other repo, I don't see how this is a bug. It's documented that ReactivityTransform will transform `$()` in any projects files. So if you activate this transform, don't use that function name for anything else. Specifically, likely: don't use JQuery.
>
> You also say how it's ... | 2023-01-11T07:40:32 | 2023-01-11T07:40:32 | {} | NONE |
vuejs | core | 1,378,801,565 | 7,048 | sxzz | @RomainLanz Could you please provide a minimum reproduction repo? | 2023-01-11T14:04:43 | 2023-01-11T14:04:43 | {} | MEMBER |
vuejs | core | 1,380,180,316 | 6,312 | taye | I've closed my PR. If you decide the best solution is to remove the brackets when transforming `$$`, I can try to make a PR for that and include the tests from my previous PR. | 2023-01-12T11:19:38 | 2023-01-12T11:19:38 | {
"eyes": 1
} | NONE |
vuejs | core | 1,380,317,756 | 7,509 | LinusBorg | > I am thinking I need some kind of hydration solution here.
I agree. But your requirements are very vague from my perspective. This is, in its current state, not a feature request, this is a question on basically how to do client-side hydration of HMTL that comes from a CMS, not a server running Vue SSR on node.
... | 2023-01-12T13:06:37 | 2023-01-12T13:06:37 | {} | MEMBER |
vuejs | core | 1,374,697,124 | 7,481 | RosApr | > ```diff
> - function handleUpdate(type) {
> + async function handleUpdate(type) {
> if(type ===timeMetrics.value) {return}
> timeMetrics.value = type
> console.log(timeMetrics.value)
> selectedColumns.value= [{title: 'demo'}, ...makeTableColumns(type)]
> console.log('parent', selectedColumn... | 2023-01-08T03:21:32 | 2023-01-08T03:21:32 | {} | NONE |
vuejs | core | 1,379,659,347 | 5,540 | j4hangir | > I too have this problem but I got to say that it's not consistent. Some components work and other don't. I can't put a finger on a reason why. They all use `defineExpose` normally.
>
> It seems to affect components that are conditionally rendered via a `v-if` but the stackblitz example does not do this, so I have ... | 2023-01-12T00:35:38 | 2023-01-12T00:35:38 | {} | NONE |
vuejs | core | 1,380,054,692 | 7,510 | GRPdream | @LinusBorg Hoping to help approval workflow and review code #7355 | 2023-01-12T09:41:35 | 2023-01-12T09:41:35 | {} | CONTRIBUTOR |
vuejs | core | 1,380,188,053 | 7,509 | unsalkorkmaz | PWA is a nice thing to have. Main problem of PWA is; it is basically useless in javascript disabled situations, Open Graph support and SEO.. even with crawler bots' effort. SSR and SSG are current solutions but what if we don't use node.js server or static content? apache/nginx CMS systems are pretty common thing.
F... | 2023-01-12T11:26:28 | 2023-01-12T11:30:17 | {} | NONE |
vuejs | core | 1,373,367,989 | 5,707 | mrspartak | Can confirm, but is there on 3.2.45 | 2023-01-06T09:02:17 | 2023-01-06T09:02:17 | {} | NONE |
vuejs | core | 1,374,522,797 | 7,477 | LinusBorg | You can do that in a custom directive. | 2023-01-07T15:51:45 | 2023-01-07T15:51:45 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,374,762,914 | 7,479 | zhangzhonghe | ```html
<Page>
<PageHeader>
header content goes here
</PageHeader>
<PageBody>
body goes here
</PageBody>
</Page>
```
The above code means the same as the following code in terms of the current semantics:
```html
<Page>
<template v-slot:default>
<PageHeader>
header content ... | 2023-01-08T08:47:32 | 2023-01-08T08:53:57 | {} | MEMBER |
vuejs | core | 1,375,334,751 | 7,486 | sxzz | Use `refDebounced` from VueUse instead.
Doc: https://vueuse.org/shared/refDebounced/ | 2023-01-09T09:35:54 | 2023-01-09T09:35:54 | {} | MEMBER |
vuejs | core | 1,376,586,841 | 7,476 | edison1105 | see https://github.com/vuejs/vue/issues/4094 | 2023-01-10T01:16:37 | 2023-01-10T01:16:37 | {} | MEMBER |
vuejs | core | 1,378,460,871 | 7,496 | sxzz | FYI: https://github.com/vuejs/babel-plugin-jsx#custom-directive | 2023-01-11T09:26:21 | 2023-01-11T09:26:21 | {} | MEMBER |
vuejs | core | 1,378,897,307 | 7,048 | RomainLanz | Yes, it does fix it! | 2023-01-11T15:05:13 | 2023-01-11T15:05:13 | {} | NONE |
vuejs | core | 1,380,144,429 | 7,515 | LinusBorg | Thats intended and documented as such. Yes, sometimes workarounds are necessary in edge cases. But more often than not, you *want* this to be able to i.e. position a child component with css. | 2023-01-12T10:50:19 | 2023-01-12T10:50:19 | {} | MEMBER |
vuejs | core | 1,375,361,068 | 7,487 | jacekkarczmarczyk | Duplicate of https://github.com/vuejs/core/issues/7177? And/or maybe https://github.com/vuejs/core/issues/5847 | 2023-01-09T10:00:48 | 2023-01-09T10:00:48 | {} | CONTRIBUTOR |
vuejs | core | 1,375,401,080 | 7,487 | jacekkarczmarczyk | > suggests to simply declare boolean props as required
The problem with that is that my IDE (JetBrains) shows me the warning that component is missing required prop if I don't provide it. Not sure if this is a problem on IDE or Vue side | 2023-01-09T10:29:15 | 2023-01-09T10:29:15 | {} | CONTRIBUTOR |
vuejs | core | 1,381,467,079 | 7,525 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | cc72b8c1940e7d5ff5134aca107215def3c9a39f |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-13T08:21:35 | 2023-01-13T08:21:35 | {} | NONE |
vuejs | core | 1,370,646,583 | 5,961 | sxzz | FYI Vue Macros implemented this feature.
https://vue-macros.sxzz.moe/macros/define-slots.html
relate RFC https://github.com/vuejs/core/pull/2693 | 2023-01-04T09:04:45 | 2023-01-04T09:05:49 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,372,624,366 | 5,697 | amery | this seems to be related to "tree shaking". any idea how to prevent it? | 2023-01-05T19:11:17 | 2023-01-05T19:11:17 | {} | NONE |
vuejs | core | 1,374,845,175 | 7,475 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 3798471d4247cc85eea02f349343104b2d855151 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-08T14:07:16 | 2023-01-08T14:07:16 | {} | NONE |
vuejs | core | 1,375,135,009 | 7,484 | lizidev | please refer to https://vuejs.org/guide/built-ins/transition.html#css-based-transitions
modify minimal reproduction:
https://sfc.vuejs.org/#eNp9Ustu2zAQ/BWCQJEWiEQ1bS6qEqT/0CMvtLSKmfIFcqXEMPzvWZK24yRAbpyZ3RkuuXv+N4R2XYD3fEhj1AFZAlzCvXTaBh+R7VmEmR3YHL1lV1R6JZ10o3eJSrf+md3lgu8YF/gh3SCqC/UTQLDBKARCjA3/wECxRH8n+cZPO8mLkr... | 2023-01-09T05:55:04 | 2023-01-09T05:55:04 | {} | NONE |
vuejs | core | 1,378,760,434 | 7,048 | RomainLanz | Hey there! 👋🏻
This was fixed in `3.2.41`, but it seems to happen again in `3.2.45`.
```
TS4058: Return type of exported function has or is using name 'RawSymbol' from external module "/workspace/node_modules/.pnpm/@vue+reactivity@3.2.45/node_modules/@vue/reactivity/dist/reactivity" but cannot be named.
``` | 2023-01-11T13:33:53 | 2023-01-11T13:33:53 | {
"+1": 2
} | NONE |
vuejs | core | 1,379,804,676 | 7,492 | zhangzhonghe | 看起来像是 [vuejs/router](https://github.com/vuejs/router) 的 ```router-view``` 组件的问题。
因为你在二级路由的地方使用了 ```keep-alive``` ，所以在切换路由的时候对应的二级路由组件没有被销毁。这些没有被销毁的组件在路径变更时还会被触发更新，所以就导致了该问题的出现。
希望你能在 [vuejs/router](https://github.com/vuejs/router) 提一个 Issue 以帮助我们记录并解决这个问题（最好使用英文），非常感谢！ | 2023-01-12T04:39:02 | 2023-01-12T04:39:02 | {} | MEMBER |
vuejs | core | 1,371,843,827 | 7,425 | xiaoxiangmoe | LGTM | 2023-01-05T06:49:51 | 2023-01-05T06:49:51 | {} | CONTRIBUTOR |
vuejs | core | 1,374,280,802 | 7,478 | AlttiRi | Is `toRaw` should not return the original type without any change? | 2023-01-07T00:05:33 | 2023-01-07T00:05:33 | {} | NONE |
vuejs | core | 1,375,390,084 | 7,177 | LinusBorg | Expected and documented behavior. Missing Boolean props are cast to `false` every since Vue 2 at least. I get the confusion this may cause, but that API is set like this until we talk about breaking changes for Vue 4 some time in the future.
https://vuejs.org/guide/components/props.html#boolean-casting
I get thou... | 2023-01-09T10:20:21 | 2023-01-09T10:22:49 | {} | MEMBER |
vuejs | core | 1,375,397,515 | 7,177 | jacekkarczmarczyk | > Expected and documented behavior
Could you please point me to the docs section saying that the type of `?: boolean` prop (which as I understand would be equivalent of `{ type: Boolean }` in object syntax) is `boolean | undefined` although the value is never `undefined` (even when we pass `undefined` explicitely) a... | 2023-01-09T10:26:03 | 2023-01-09T10:26:03 | {} | CONTRIBUTOR |
vuejs | core | 1,375,504,456 | 7,479 | LinusBorg | This is not even a breaking change, strictly speaking, but it inverts responsibilities and opens up a lot of questions both technically and from a DX perspective.
* Technical: This change would require the compiler to be aware of the child component's "slot setting. this means, we can no longer compile an SFC on its... | 2023-01-09T11:44:41 | 2023-01-09T11:44:41 | {} | MEMBER |
vuejs | core | 1,376,363,310 | 7,484 | danyo1399 | Okay. Thanks for your explanation. Feels like it needs one more css class for after like
from-class, from-to-class, "from-to-after". Im not sure the point of from-to-class removing on transition end but yeah relying on css specificity for Transition component is not ideal.
The actual use case is a slide up menu f... | 2023-01-09T21:40:00 | 2023-01-09T21:40:00 | {} | NONE |
vuejs | core | 1,376,996,514 | 6,812 | matej-svejda | > @posva @Akryum We hit a serious performance issue in dev mode in Vue v3.2.41 vs v3.2.40 which forced us to pin our version and we suspect it was caused by this PR as the performance tools point to `cleanupBuffer`. This is on a page which mounts/unmounts components rather rapidly, when I have the time I'll try to crea... | 2023-01-10T09:53:59 | 2023-01-10T09:54:10 | {} | NONE |
vuejs | core | 1,372,159,925 | 7,466 | WillAvudim | Yep, both suggestions seem to address the problem fully. Sorry to have bugged you! Happy New Year! | 2023-01-05T12:33:54 | 2023-01-05T12:33:54 | {} | NONE |
vuejs | core | 1,374,763,707 | 7,479 | denjaland | Yes, I realise this. However, since a component in itself is a template, it feels like we have nested <template> tags now.
I very much know it might be a breaking change, but it still feels like one I would enjoy ;-) | 2023-01-08T08:50:17 | 2023-01-08T08:50:17 | {} | NONE |
vuejs | core | 1,375,326,671 | 7,485 | edison1105 | see https://github.com/vuejs/core/pull/6659 and https://github.com/vuejs/core/pull/4443#issuecomment-1259205410
you should report it to naive-ui.
| 2023-01-09T09:28:27 | 2023-01-09T09:30:59 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.