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,375,923,737 | 7,487 | LinusBorg | It is a bug because a boolean component prop **cannot** be undefined in Vue, it will **always** be cast to `false` at runtime. so the types should reflect that.
This is Vue-specific, so taking Vue out of the picture makes no sense. | 2023-01-09T16:38:37 | 2023-01-09T18:00:13 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,377,844,631 | 7,500 | camsteffen | Oh goodness. I just found the "Composition" toggle in the upper left corner of the docs page. Totally missed that. I think that switch needs to be more prominent somehow. | 2023-01-10T20:59:18 | 2023-01-10T20:59:18 | {} | NONE |
vuejs | core | 1,378,843,418 | 7,048 | RomainLanz | Sure, it happens when using a "complex" typing from `@tanstack/vue-query`.
```ts
async function fetchFoo() {
return markRaw({ foo: 'bar' });
}
export function useFoo(options?: UseQueryOptions<Awaited<ReturnType<typeof fetchFoo>>>) {
return useQuery({
queryKey: ['foo'],
queryFn: fetchFoo,
..... | 2023-01-11T14:33:50 | 2023-01-11T14:33:50 | {} | NONE |
vuejs | core | 1,379,887,179 | 7,412 | houd1ni | Hi, @LinusBorg ! Just for info. I faced the same bug using vite 4.0.4 with HMR: any hyphenated attributes to custom components weren't recognized as props and go HTML. After Ctrl+R vue hyphens them as it should. | 2023-01-12T06:52:21 | 2023-01-12T06:52:21 | {} | NONE |
vuejs | core | 1,380,254,349 | 7,518 | baiwusanyu-c | please add a unit test | 2023-01-12T12:26:28 | 2023-01-12T12:26:28 | {} | MEMBER |
vuejs | core | 1,371,111,577 | 7,444 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | cc506ce99b1aa04c65522e8879fca9853fceed09 |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2023-01-04T16:00:05 | 2023-01-04T16:00:05 | {} | NONE |
vuejs | core | 1,374,504,837 | 7,481 | zhangzhonghe | ```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', selectedColumns.value)
+ aw... | 2023-01-07T14:50:33 | 2023-01-07T14:50:33 | {} | MEMBER |
vuejs | core | 1,377,332,388 | 7,495 | syntony | Sorry, my bad - faced it working with Vue project. It seems the issue is Google Chrome behaviour in this situation and devices, e.g. Mozilla Firefox working fine. For example, same issue detected with React + input
![Screenshot_20230110-155753](https://user-images.githubusercontent.com/19506390/211571306-bc31d241-520a... | 2023-01-10T14:03:45 | 2023-01-10T14:03:45 | {
"+1": 2
} | NONE |
vuejs | core | 1,379,943,303 | 6,861 | lsdsjy | > A better workaround:
>
> ```css
> ~ :deep(h1),
> :deep(h1) {
> color: red;
> }
> ```
@abitwhy That's clever but won't work if I move `<Comp1>` to the beginning of `<template>` (i.e. make it the first child) | 2023-01-12T08:01:59 | 2023-01-12T08:02:32 | {} | NONE |
vuejs | core | 1,380,014,159 | 5,657 | Anubarak | I also face this issue but I have no idea how to fix it nor do I know where exactly the issue occurs.
It happens in production and dev mode with [PrimeVue ](https://github.com/primefaces/primevue) when I use nested tabs https://primefaces.org/primevue/tabview.
Sometimes when changing from one tab to another via UR... | 2023-01-12T09:08:00 | 2023-01-12T09:08:00 | {} | NONE |
vuejs | core | 1,371,334,840 | 7,465 | isaacspigen | This project I am working on did not had tsconfig.json.
After creating one with basic options, the issue was gone. | 2023-01-04T19:32:04 | 2023-01-04T19:32:04 | {} | NONE |
vuejs | core | 1,371,900,056 | 7,466 | LinusBorg | Sounds like you could use a detatched [effectScope](https://vuejs.org/api/reactivity-advanced.html#effectscope).
That's also what i.e. pinia uses to keep the stores detatched from the lifecycle of the components that consume them.
A more hacky approach would be to simply create the watcher on the next Tick, when ... | 2023-01-05T08:09:27 | 2023-01-05T08:47:08 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,374,268,274 | 7,478 | AlttiRi | However, `readonly` type modifier is only permitted on array and tuple literal types. (`TS1354`)
In this case there is a problem anyway:
```ts
class A {
// get selves(): [A] { // same thing
// return [this];
// }
children: A[]
}
const a: Ref<A> = ref(new A());
const b: D... | 2023-01-06T23:45:42 | 2023-01-07T11:59:48 | {} | NONE |
vuejs | core | 1,378,544,425 | 4,052 | yalcinyagizkorkmaz | runtime-core.esm-bundler.js?d2dd:40 [Vue warn]: Failed to resolve component: router-link
If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.
at <App>
warn @ runtime-core.esm-bundler.js?d2dd:40
runtime-core.esm-bundler.js?d2dd:40 [Vue warn]: F... | 2023-01-11T10:34:02 | 2023-01-11T10:34:02 | {} | NONE |
vuejs | core | 1,373,722,829 | 5,764 | richardtallent-erm | I'm not sure if I should raise a separate issue or not. I'm seeing the same problem with a normal SFC (with TS enabled) and slots:
```vue
<NavList v-slot="{ item } as { item: IMenuModel }" :items="state.items">
<div>{{ item.title }}</div>
</NavList>
...
<script setup lang="ts">
</script>
```
The above ... | 2023-01-06T14:41:20 | 2023-01-06T14:41:20 | {
"+1": 2
} | NONE |
vuejs | core | 1,374,708,689 | 7,481 | zhangzhonghe | @RosApr I'm sorry! I can't follow your point.
In Vue, when the component's state changes, the component is updated asynchronously. So if you want to get the latest props, you must wait for the component to finish updating. | 2023-01-08T04:51:07 | 2023-01-08T04:51:07 | {} | MEMBER |
vuejs | core | 1,374,996,606 | 7,392 | edison1105 | > From my perspective v-model should set value during beforeMount hook before the element is inserted into DOM
It's probably something that can be optimized
| 2023-01-09T01:21:51 | 2023-01-09T01:23:51 | {} | MEMBER |
vuejs | core | 1,375,336,777 | 7,484 | danyo1399 | i still dont think its working. It only happens to work due to the css ordering. Actually both classes are applied. if i take your example and move the .from class above the .common class it doesnt work again. Thats important because you might not have control over the ordering of css eg tailwind
https://sfc.vuejs.o... | 2023-01-09T09:37:49 | 2023-01-09T09:37:49 | {} | NONE |
vuejs | core | 1,375,336,525 | 7,486 | sxzz | I think it's not a core feature of reactivity, so we should not expect it's implemented by Vue core but by Vue's ecosystem projects. | 2023-01-09T09:37:39 | 2023-01-09T09:38:11 | {} | MEMBER |
vuejs | core | 1,378,842,727 | 7,497 | SavkaTaras | Hello @LinusBorg ,
Thank you for the clarification on this matter. This is a good point. It would be nice to have booleans present but we understand you have much more pressing matters on your plate.
Thank you again,
Taras | 2023-01-11T14:33:20 | 2023-01-11T14:33:20 | {} | NONE |
vuejs | core | 1,368,411,596 | 7,444 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | cc506ce99b1aa04c65522e8879fca9853fceed09 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-01T10:49:01 | 2023-01-04T16:01:45 | {} | NONE |
vuejs | core | 1,371,266,001 | 7,464 | sxzz | relate issue #6312
relate PR #6303 #7279 #6944
my relate comment https://github.com/vuejs/core/pull/7279#issuecomment-1345359088 | 2023-01-04T18:18:18 | 2023-01-04T18:20:29 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,372,015,502 | 2,097 | Fuzzyma | @yyx990803 are there any considerations around this topic? You mentioned this could be a documented feature and not just a hack. | 2023-01-05T10:06:25 | 2023-01-05T10:06:25 | {
"+1": 1
} | NONE |
vuejs | core | 1,374,522,498 | 5,764 | LinusBorg | > error from ESLint
So: not related to this issue, not even this repository. related to `eslint-plugin-vue` | 2023-01-07T15:50:41 | 2023-01-07T15:51:14 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,375,138,274 | 7,481 | RosApr | > @RosApr I'm sorry! I can't follow your point.
>
> In Vue, when the component's state changes, the component is updated asynchronously. So if you want to get the latest props, you must wait for the component to finish updating.
got it! thx | 2023-01-09T06:01:48 | 2023-01-09T06:01:48 | {} | NONE |
vuejs | core | 1,375,393,812 | 7,487 | LinusBorg | @jacekkarczmarczyk Not really a duplicate of #7177. In fact, #7177 can be closed as it is expected behavior (https://github.com/vuejs/core/issues/7177#issuecomment-1375390084).
#5847 seems to be related and likely solved when this issue here is solved, which seems to be the underlying issue for #5847.
Looking at t... | 2023-01-09T10:23:18 | 2023-01-09T10:24:59 | {} | MEMBER |
vuejs | core | 1,378,779,528 | 7,505 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 88e1a382831fd1a4d8f10f35a15ab772762af230 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-11T13:48:28 | 2023-01-11T13:58:27 | {} | NONE |
vuejs | core | 1,364,488,965 | 7,412 | LinusBorg | @yyx990803 This is my second attempt at tackling this.
You wrote in my previous PR it would not be the right fix as it would conflict with SVG attributes, but this one here should respect `isSVG`.
You also wrote that you see the original issue in #5477 as being more about slot props not being camelized, but I th... | 2022-12-24T08:39:55 | 2023-01-12T06:54:31 | {} | MEMBER |
vuejs | core | 1,379,912,023 | 7,509 | LinusBorg | Can you provide a little more context? I don't see any connection between Teleport and v-html, so I don't really get what you are asking for. | 2023-01-12T07:24:19 | 2023-01-12T07:24:19 | {} | MEMBER |
vuejs | core | 1,380,136,115 | 7,516 | LinusBorg | Well, errors need handling - by you, preferably. And should not go unnoticed, ignored by the framework. Some errors, by their nature, will break the render cycle of Vue and thus will break (a part of the) the app.
Vue provides you with ways to handle errors thrown within its lifecycle:
https://vuejs.org/api/comp... | 2023-01-12T10:42:48 | 2023-01-12T10:43:16 | {} | MEMBER |
vuejs | core | 1,380,153,432 | 2,047 | fanckush | any updates on this | 2023-01-12T10:57:30 | 2023-01-12T10:57:30 | {} | NONE |
vuejs | core | 1,372,010,891 | 7,392 | eddeisling | @edison1105 thank you for the info, extremely interesting!
But does it mean that vue renders input without taking into account the initial value of `v-model`?
https://sfc.vuejs.org/#eNqVUk1v2zAM/SuELnGB2Ma... | 2023-01-05T10:02:34 | 2023-01-05T10:18:50 | {} | NONE |
vuejs | core | 1,374,206,034 | 7,478 | AlttiRi | I figure out how to fix it.
I need to use `readonly` when I pass `DeepReadonly` into `toRaw`:
```ts
// It works
const a2: Ref<TypeA[]> = ref([{a: "a1"}, {a: "a2"}]);
const b2: DeepReadonly<Ref<TypeA[]>> = readonly(a2);
const c2: readonly TypeA[] = toRaw(b2.value);
```
Is it planned beh... | 2023-01-06T22:27:13 | 2023-01-07T00:04:40 | {} | NONE |
vuejs | core | 1,375,416,893 | 7,177 | jacekkarczmarczyk | > Can we continue discussion about that bug in that new issue, as it doesn't have two topics intertwined?
I was just about to write that my issue is also about the type, that's fine, let's keep the discussion in the other issue
| 2023-01-09T10:43:59 | 2023-01-09T10:43:59 | {} | CONTRIBUTOR |
vuejs | core | 1,375,545,730 | 7,479 | denjaland | Hi @LinusBorg,
Thanks for the reply, and yes: I totally agree with your remarks / views.
Some feedback / questions I have:
- 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. Also, for th... | 2023-01-09T12:19:45 | 2023-01-09T12:20:50 | {} | NONE |
vuejs | core | 1,378,347,020 | 7,501 | LinusBorg | And finally, If you want to argue for a plugin option to restrict the transform to specific folders: That would be a *feature request* for vite-plugin-vue, not us.
https://github.com/vitejs/vite-plugin-vue/blob/main/packages/plugin-vue/src/script.ts#L56 | 2023-01-11T07:39:35 | 2023-01-11T07:39:35 | {} | MEMBER |
vuejs | core | 1,312,425,925 | 7,116 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | bffb1b2aea57d860719f72908bee19e4dcde0b63 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-11-12T09:38:51 | 2023-01-12T05:56:11 | {} | NONE |
vuejs | core | 1,380,159,815 | 7,518 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 080fbf5efd3463151fe207a47049ca85fc9056c0 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-12T11:02:52 | 2023-01-13T03:30:08 | {} | NONE |
vuejs | core | 1,425,723,193 | 7,432 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4143731114)
| suite | result |
|-------|--------|
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4143731114/jobs/7165936485) | :white_check_mark: success |
| [pinia](https://github.com/vuejs/ecosystem-ci/actions/runs/41437311... | 2023-02-10T12:08:37 | 2023-02-10T12:13:22 | {} | CONTRIBUTOR |
vuejs | core | 1,427,097,678 | 7,115 | lexiesanchez | >
How was it fixed? Currently having this issue | 2023-02-12T18:15:51 | 2023-02-12T18:15:51 | {
"+1": 1,
"eyes": 1
} | NONE |
vuejs | core | 1,429,248,540 | 7,707 | liuseen-l | v3在设计上就是会判断是否以$开头，当不是以$开头才会去props当中获取数据
```
if (key[0] !== '$') {
const n = accessCache![key]
if (n !== undefined) {
switch (n) {
case AccessTypes.SETUP:
return setupState[key]
case AccessTypes.DATA:
return data[key]
case AccessTypes... | 2023-02-14T07:20:40 | 2023-02-14T07:20:40 | {} | CONTRIBUTOR |
vuejs | core | 1,429,346,075 | 1,342 | pangao66 | here I have a case
when the dom is a empty dom, it show - ;
it often used in a table, when the cell is empty , show a hyphen
I can use empty css selectors to select the empty cell
```
.ant-table-cell{
&:empty {
&:after {
content: '-';
}
}
}
```
but if the dom is em... | 2023-02-14T08:50:16 | 2023-02-14T09:00:45 | {} | NONE |
vuejs | core | 1,427,217,558 | 7,696 | JayFate | After this commit
| 2023-02-13T01:57:50 | 2023-02-13T01:57:50 | {} | CONTRIBUTOR |
vuejs | core | 1,427,517,273 | 7,695 | AlexVagrant | Your `if` condition controls when registers `onCleanup` function. it does not control when `vue` call `onCleanup` function.
If you register an `onCleanup` function it would always exist. so you will see the `watch` method is triggered, and the `onCleanup` method is also triggered
| 2023-02-13T08:13:31 | 2023-02-13T08:13:31 | {} | CONTRIBUTOR |
vuejs | core | 1,430,946,699 | 3,231 | rudolfbyker | - I made a minimal reproduction repository for the problem: https://github.com/rudolfbyker/vue-pug-indent-reproduction
- Here is an old PR trying to address the problem: https://github.com/vuejs/core/pull/3842
- Here is my new PR: https://github.com/vuejs/core/pull/7723 | 2023-02-15T08:40:33 | 2023-02-15T09:21:48 | {} | NONE |
vuejs | core | 1,425,695,814 | 7,339 | haoqunjiang | /ecosystem-ci run | 2023-02-10T11:46:20 | 2023-02-10T11:46:20 | {} | MEMBER |
vuejs | core | 1,426,410,881 | 7,688 | LinusBorg | Yes | 2023-02-10T22:16:55 | 2023-02-10T22:16:55 | {} | MEMBER |
vuejs | core | 1,426,695,234 | 7,688 | LinusBorg | Got it. when calling `suspense.registerDep`, we don't pass the current value of `optimize`. Instead, in `registerDep`, we use the closure's value of `optimized` that was passed to `createSusenseBoundary()`
https://github.com/vuejs/core/blob/1d09540798bdb22ce6d1579688e041c8b8c3f730/packages/runtime-core/src/renderer.... | 2023-02-11T10:44:45 | 2023-02-11T10:46:27 | {
"heart": 1,
"hooray": 1
} | MEMBER |
vuejs | core | 1,426,821,453 | 7,365 | sxzz | /ecosystem-ci run | 2023-02-11T16:52:02 | 2023-02-11T16:52:02 | {} | MEMBER |
vuejs | core | 1,425,762,848 | 7,365 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4144006140)
| suite | result |
|-------|--------|
| [element-plus](https://github.com/vuejs/ecosystem-ci/actions/runs/4144006140/jobs/7166545760) | :x: failure |
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4144006140/jobs/... | 2023-02-10T12:46:35 | 2023-02-11T16:52:15 | {} | CONTRIBUTOR |
vuejs | core | 1,426,825,484 | 7,394 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4152311081)
| suite | result |
|-------|--------|
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4152311081/jobs/7183187018) | :white_check_mark: success |
| [pinia](https://github.com/vuejs/ecosystem-ci/actions/runs/41523110... | 2023-02-11T17:01:36 | 2023-02-11T17:07:17 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,426,861,250 | 7,688 | olfek | Thank you for triaging this and finding a fix so quickly, much appreciated @LinusBorg ❤️ | 2023-02-11T19:37:15 | 2023-02-11T19:37:15 | {} | NONE |
vuejs | core | 1,427,210,166 | 7,685 | huzedong2015 | > Closing this as I don't see any problem
I filled out the expected and actual data inversely | 2023-02-13T01:44:54 | 2023-02-13T01:44:54 | {} | NONE |
vuejs | core | 1,430,655,919 | 7,700 | Autumn-one | > ```
> <template>
> <div>Test组件</div>
> </template>
>
> <script lang="ts" setup>
> import { watch, nextTick, } from 'vue';
>
> const props = defineProps(['foo', 'debugName']);
> const emit = defineEmits(['update:foo']);
>
> watch(
> () => props.foo,
> async () => {
> console.log(pr... | 2023-02-15T02:15:36 | 2023-02-15T02:15:36 | {} | NONE |
vuejs | core | 1,430,992,816 | 7,708 | edison1105 | @han1822815550
你的组件名是 Priceterms.vue 么？如果是还不能正常被 keep-alive 的话，请提供一个最小可复现的 demo。
| 2023-02-15T09:15:21 | 2023-02-15T09:15:21 | {} | MEMBER |
vuejs | core | 1,430,997,505 | 7,708 | han1822815550 | > @han1822815550 你的组件名是 Priceterms.vue 么？如果是还不能正常被 keep-alive 的话，请提供一个最小可复现的 demo。
路由里name是Priceterms，组件文件名是index.vue（priceterms文件夹下的index.vue），然后index.vue中没手动声明name | 2023-02-15T09:19:05 | 2023-02-15T09:19:05 | {} | NONE |
vuejs | core | 1,425,765,446 | 2,015 | stpnov | I offer my solution based on the suggestion above:
```TypeScript
import {defineComponent, DefineComponent, h, ShallowRef, shallowRef, Teleport, VNode} from 'vue'
type PortalKey = PropertyKey
const portals: Map<PortalKey, ShallowRef<VNode | undefined>> = new Map()
function getTargetRef(key: PortalKey): Shallo... | 2023-02-10T12:49:21 | 2023-02-10T12:52:18 | {
"+1": 2
} | NONE |
vuejs | core | 1,426,348,920 | 7,688 | olfek | Creating the minimal reproduction, I've learned that it has something to do with:
- `<Suspense>` in `App.vue`
- The use of `await` in `HomeView.vue` | 2023-02-10T21:07:43 | 2023-02-10T21:07:43 | {} | NONE |
vuejs | core | 1,426,408,530 | 7,688 | olfek | Have you been able to reproduce it @LinusBorg ? Is this now a confirmed bug? | 2023-02-10T22:14:20 | 2023-02-10T22:14:20 | {} | NONE |
vuejs | core | 1,426,825,374 | 7,394 | sxzz | /ecosystem-ci run | 2023-02-11T17:01:11 | 2023-02-11T17:01:11 | {} | MEMBER |
vuejs | core | 1,428,140,992 | 5,688 | vampics | @yyx990803 @posva I think that this information should be added to the docs. It took me a little while until I landed here in this issue.
Despite this logic hole, I think this should be possible - even with extra settings to become aware of the behaviour. We have a framework with more than 100 components that contai... | 2023-02-13T15:28:42 | 2023-02-13T15:35:54 | {} | NONE |
vuejs | core | 1,429,988,055 | 4,662 | SavkaTaras | > As a simple workaround exclude the styles into a css-file and import it inside the `<style>` tag of the `main.ce.vue` file.
Hi,
This would get very messy if you have a design system in place that re-uses components. | 2023-02-14T16:03:28 | 2023-02-14T16:03:28 | {} | NONE |
vuejs | core | 1,430,656,666 | 7,700 | Autumn-one | > The reason is that by the time the second watcher's getter is run, `props.foo` has been reset to `false` already by the first watcher's callback.↳
>
> The getter function (`() => props.foo`) _does_ run for the second watcher, but the callback won't be run because the getter's return values hasn't changed - it was ... | 2023-02-15T02:16:52 | 2023-02-15T02:16:52 | {} | NONE |
vuejs | core | 1,425,743,649 | 7,432 | haoqunjiang | The Ecosystem CI is all green now. But the snapshot test failed, and I can't understand the error message. Could you take a look? | 2023-02-10T12:26:50 | 2023-02-10T12:26:50 | {} | MEMBER |
vuejs | core | 1,426,862,767 | 7,688 | LinusBorg | yes | 2023-02-11T19:45:09 | 2023-02-11T19:45:09 | {} | MEMBER |
vuejs | core | 1,425,933,246 | 7,685 | LinusBorg | Yeah, I can't see the described problem either. SFC playground example works as desired. | 2023-02-10T15:04:50 | 2023-02-10T15:04:50 | {} | MEMBER |
vuejs | core | 1,426,884,234 | 2,818 | unitydynamics | This change broke userland types that extends SetupContext. My code that type-checks emit signatures no longer works.
I had this utility interface:
```
interface SetupContextExtended<Event extends Record<string, any>> extends SetupContext {
emit: <Key extends keyof Event>(event: Key, payload: Event[Key]) =>... | 2023-02-11T21:53:50 | 2023-02-11T22:07:57 | {} | NONE |
vuejs | core | 1,427,683,976 | 6,219 | jiangshengdev | #7702
My idea can solve this problem, and it has been used in production. But the harm is great. Welcome to discuss and propose better solutions | 2023-02-13T10:20:14 | 2023-02-13T10:20:14 | {} | NONE |
vuejs | core | 1,429,334,828 | 7,707 | AlexVagrant | I think this is the same problem with https://github.com/vuejs/core/issues/7710
`should not start with "$" or "_" which are reserved prefixes for Vue internals.` | 2023-02-14T08:40:06 | 2023-02-14T08:40:06 | {} | CONTRIBUTOR |
vuejs | core | 1,430,020,514 | 6,908 | DmitryTar1 | @LinusBorg @yc-huang Is there any updates? Still have this issue and it stops from continue with vue3 migration. | 2023-02-14T16:22:29 | 2023-02-14T16:22:29 | {
"+1": 1
} | NONE |
vuejs | core | 1,425,674,329 | 7,218 | xieyuheng | Is it possible to define `v-scope` as an user defined directive? | 2023-02-10T11:33:51 | 2023-02-10T11:33:51 | {} | NONE |
vuejs | core | 1,426,365,948 | 7,688 | olfek | - Replacing `await` with `void` in `HomeView.vue` makes the problem go away.
- `<Suspense>` was added in `App.vue` because without it, the use of `await` in `HomeView.vue` gives errors. | 2023-02-10T21:27:30 | 2023-02-10T21:27:30 | {} | NONE |
vuejs | core | 1,426,397,243 | 7,688 | LinusBorg | <img width="1049" alt="Bildschirmfoto 2023-02-10 um 23 00 11" src="https://user-images.githubusercontent.com/1444526/218207165-f2fe16ec-c082-414f-b2f1-661733b2de9c.png">
`patchFlag` is `0`, so it should receive a full props diff, but `optimized` is `true`, so line 3823 evaluates to true, so the code enters that bra... | 2023-02-10T22:02:14 | 2023-02-10T22:38:40 | {} | MEMBER |
vuejs | core | 1,426,821,519 | 7,365 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4152282765)
| suite | result |
|-------|--------|
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4152282765/jobs/7183137692) | :white_check_mark: success |
| [pinia](https://github.com/vuejs/ecosystem-ci/actions/runs/41522827... | 2023-02-11T16:52:24 | 2023-02-11T16:57:12 | {} | CONTRIBUTOR |
vuejs | core | 1,426,996,187 | 7,685 | LinusBorg | Closing this as I don't see any problem | 2023-02-12T10:30:35 | 2023-02-12T10:30:35 | {} | MEMBER |
vuejs | core | 1,427,263,319 | 2,775 | sakurawald | > 1. use `defineComponent()` to let TS know you are actually defining a Vue component
> 2. try annotating the return values of the computed's:
>
> ```ts
> showMachines(): boolean {
> ```
>
> For more help, please use chat.vuejs.org
This works. The problem of TypeScript | 2023-02-13T03:02:25 | 2023-02-13T03:02:25 | {} | NONE |
vuejs | core | 1,427,877,021 | 6,225 | hminghe | 已经修复了。 | 2023-02-13T12:41:24 | 2023-02-13T12:41:24 | {} | NONE |
vuejs | core | 1,429,882,077 | 7,713 | 0x-jerry | FYI, It's also crash when pass a non-object value. For example, `v-bind="1"` and `v-bind="'aaa'"`. [playground](https://sfc.vuejs.org/#eNp9UstOwzAQ/JXFHAxSY4PKqUqjIi78ARdf3MZtAvFDthMOUf6dtVuqUAo37+zsjL3jkTw7x4ZekRUpw863LkJQsXeVMK121kcYwas9TLD3VgNFKj23Xqx2J5zxVCQlbAuzsyZE0OEA6zR+R19V11l4s76rb+i9MCU/uqEPFlFp18mosAIom8dqH... | 2023-02-14T14:58:52 | 2023-02-14T14:58:52 | {} | NONE |
vuejs | core | 1,429,976,310 | 7,717 | xiaoLi-TvT | LGTM | 2023-02-14T15:55:38 | 2023-02-14T15:55:38 | {} | NONE |
vuejs | core | 1,431,193,055 | 7,708 | edison1105 | > > @han1822815550 你的组件名是 Priceterms.vue 么？如果是还不能正常被 keep-alive 的话，请提供一个最小可复现的 demo。
>
>
>
> 路由里name是Priceterms，组件文件名是index.vue（priceterms文件夹下的index.vue），然后index.vue中没手动声明name
（在 3.2.34 或以上的版本中，使用 <script setup> 的单文件组件会自动根据文件名生成对应的 name 选项，无需再手动声明。）
keepalive是根据文件名字缓存的，跟路由没关系。
| 2023-02-15T11:18:52 | 2023-02-15T11:18:52 | {} | MEMBER |
vuejs | core | 1,425,647,851 | 5,525 | johanmolen | @liulinboyi gonna test this next week, thanks! | 2023-02-10T11:11:30 | 2023-02-10T11:11:30 | {} | NONE |
vuejs | core | 1,425,696,576 | 7,339 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4143577043)
| suite | result |
|-------|--------|
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4143577043/jobs/7165585472) | :x: failure |
| [pinia](https://github.com/vuejs/ecosystem-ci/actions/runs/4143577043/jobs/7165585... | 2023-02-10T11:46:41 | 2023-02-10T11:53:39 | {} | CONTRIBUTOR |
vuejs | core | 1,425,977,312 | 7,365 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4145342534)
| suite | result |
|-------|--------|
| [element-plus](https://github.com/vuejs/ecosystem-ci/actions/runs/4145342534/jobs/7169576767) | :x: failure |
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4145342534/jobs/... | 2023-02-10T15:33:58 | 2023-02-11T16:52:10 | {} | CONTRIBUTOR |
vuejs | core | 1,426,852,043 | 7,626 | sxzz | Please rebase your branch to the latest commit.
/cc @sodatea we have to merge main to it before checking. | 2023-02-11T18:49:51 | 2023-02-11T18:49:51 | {} | MEMBER |
vuejs | core | 1,429,529,787 | 7,711 | LinusBorg | use the ìnclude` / `exclude` options. | 2023-02-14T10:59:01 | 2023-02-14T10:59:01 | {} | MEMBER |
vuejs | core | 1,430,789,047 | 7,708 | edison1105 | `include="A,B"` A and B should be string, You're passing objects.
see [playground](https://sfc.vuejs.org/#eNq1U01r20AQ/SvDXtSCrYW2UBBKsaRjbyW3bg+ONJHVrHaX3ZHTYvzfMysljmSHkEMCNmjnvZk3nwdROJfuBxSZyEPtO0cQkAb3QxlFXe+sJyjg1tselEhlEblKzMDyGSwvwOoZrC7AA4TdVmt7/wtv4TgxEyYlygBoJKht7+BqxvqUFMlnZXI5ZRpzNDlh7/SWkF8A+U9EV+huj5B1p... | 2023-02-15T05:48:02 | 2023-02-15T05:48:02 | {} | MEMBER |
vuejs | core | 1,430,807,516 | 7,708 | han1822815550 | > `include="A,B"` A and B should be string, You're passing objects. see [playground](https://sfc.vuejs.org/#eNq1U01r20AQ/SvDXtSCrYW2UBBKsaRjbyW3bg+ONJHVrHaX3ZHTYvzfMysljmSHkEMCNmjnvZk3nwdROJfuBxSZyEPtO0cQkAb3QxlFXe+sJyjg1tselEhlEblKzMDyGSwvwOoZrC7AA4TdVmt7/wtv4TgxEyYlygBoJKht7+BqxvqUFMlnZXI5ZRpzNDlh7/SWkF8A+U9EV+huj5B1... | 2023-02-15T06:13:40 | 2023-02-15T06:13:40 | {} | NONE |
vuejs | core | 1,432,402,711 | 7,722 | Justineo | We should just remove the `<button>` outside the `<a>` and update the styles. | 2023-02-16T02:42:21 | 2023-02-16T02:42:21 | {} | MEMBER |
vuejs | core | 1,425,721,235 | 4,339 | cons2act | keep-alive这个特性可以使用了吗？ | 2023-02-10T12:06:57 | 2023-02-10T12:06:57 | {
"confused": 2
} | NONE |
vuejs | core | 1,426,663,390 | 7,688 | posva | There are other bugs with Suspense and keep alive that appear because the entering component renders before the leaving component. There are some open issues in vue router about this. But I don't recall any problem with a different behavior between dev and prod | 2023-02-11T08:43:42 | 2023-02-11T08:43:42 | {} | MEMBER |
vuejs | core | 1,427,769,153 | 7,700 | AlexVagrant | ```vue
<template>
<div>Test组件</div>
</template>
<script lang="ts" setup>
import { watch, nextTick, } from 'vue';
const props = defineProps(['foo', 'debugName']);
const emit = defineEmits(['update:foo']);
watch(
() => props.foo,
async () => {
console.log(props.debugName);
aw... | 2023-02-13T11:19:38 | 2023-02-13T11:19:38 | {} | CONTRIBUTOR |
vuejs | core | 1,427,970,037 | 6,435 | vampics | ### + 1 | 2023-02-13T13:47:47 | 2023-02-13T15:37:05 | {} | NONE |
vuejs | core | 1,431,533,807 | 5,525 | flora-le | nothing is working and gives me headache omg. The value of ref, no matter what i do (skip unwrap, binding with function and push), is a proxy and I can't access anything. When i try to access with myArray.value[0], it gives undefined
![image](https://user-images.githubusercontent.com/103944447/219069446-052da381-dea... | 2023-02-15T15:17:57 | 2023-02-15T15:17:57 | {
"+1": 3
} | NONE |
vuejs | core | 1,426,834,543 | 7,626 | liuseen-l | It doesn't seem to be the problem of pr code | 2023-02-11T17:39:08 | 2023-02-11T17:39:08 | {} | CONTRIBUTOR |
vuejs | core | 1,427,466,128 | 7,685 | LinusBorg | Correct | 2023-02-13T07:23:50 | 2023-02-13T07:23:50 | {} | MEMBER |
vuejs | core | 1,428,084,864 | 7,703 | LinusBorg | This would need to be addressed in the `vue-class-component` repo - which is in need of someone actually maintaining it.
Normal classes work fine like this:
https://sfc.vuejs.org/#eNp9UMtugzAQ/JWtL6RSsJVrRCL11j9oDr4QshAiv7Rr6AHx712gqqJW6s3z8GhmJ/WWkh4HVEdVcUN9ysCYh3S2ofcpUoYJCFuYoaXooRBrYYMNTQycwXMHp0XfFe/oXISPS... | 2023-02-13T14:59:57 | 2023-02-13T14:59:57 | {} | MEMBER |
vuejs | core | 1,429,805,439 | 7,605 | atlemagnussen | If we could easily access the root html element in SFC we might not need to use Vue's special event handling | 2023-02-14T14:08:31 | 2023-02-14T14:08:31 | {} | NONE |
vuejs | core | 1,430,943,079 | 3,842 | rudolfbyker | I made a minimal reproduction repository for the problem: https://github.com/rudolfbyker/vue-pug-indent-reproduction and a new PR: https://github.com/vuejs/core/pull/7723 | 2023-02-15T08:37:14 | 2023-02-15T09:21:31 | {} | NONE |
vuejs | core | 1,432,374,309 | 7,726 | Justineo | `disabled` is a known boolean attribute for `<input>`. The breaking change described in the [docs](https://v3-migration.vuejs.org/breaking-changes/attribute-coercion.html#:~:text=Coercion%20for%20boolean%20attributes%20is%20left%20untouched.) only affects non-boolean attributes.
> Coercion for boolean attributes is ... | 2023-02-16T02:13:59 | 2023-02-16T02:13:59 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,425,663,988 | 7,218 | xieyuheng | How is this PR now?
Really really really want to use `petite-vue`'s `v-scope` in `vue3` :) | 2023-02-10T11:26:37 | 2023-02-10T11:26:37 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.