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,564,613,924 | 7,781 | niksy | Does this work on subcomponent extends? For example, I have component extended with `Vue.extend`, and another one which extends that component (`Parent.extend`). I’m still getting this warning after applying these changes. This worked in Vue 2. | 2023-05-26T16:06:29 | 2023-05-26T16:06:29 | {} | NONE |
vuejs | core | 1,556,368,394 | 8,382 | baiwusanyu-c | yo can use [defineExpose](https://vuejs.org/api/sfc-script-setup.html#defineexpose) | 2023-05-22T01:12:05 | 2023-05-22T01:12:49 | {} | MEMBER |
vuejs | core | 1,556,726,612 | 8,375 | LinusBorg | computed's are evaluated lazily - so their new return value can only be known once something actually reads its `.value`.
for that to happen though, effects depending on a computed have to be triggered - so that they than in turn can read the computed's value and it be re-evaluated.
So the behavior you are seein... | 2023-05-22T08:00:31 | 2023-05-22T08:00:31 | {} | MEMBER |
vuejs | core | 1,558,815,568 | 8,390 | coredevel | > Perhaps you can use `ButtonHTMLAttributes['disabled']`, which is exported in `runtime-dom.d.ts`.
Good spot - it was the loading prop on the IButton that has a broad 'string' type, narrowing that to HTMLButtonElement["disabled"] or explicitly as 'true' | 'false' | null worked! | 2023-05-23T08:40:25 | 2023-05-23T08:40:25 | {} | NONE |
vuejs | core | 1,559,137,166 | 8,388 | haoqunjiang | 请使用 `<script setup lang="jsx">`
不要在普通的 JS 代码块中写 JSX。
由这个 PR 引起：https://github.com/vuejs/core/pull/5846
我觉得这不能算 bug，之前的行为（把所有 JS 当 JSX 识别）才是 bug。 | 2023-05-23T11:51:55 | 2023-05-23T11:52:11 | {} | MEMBER |
vuejs | core | 1,560,034,379 | 8,400 | kevinmnm | Fixed by adding `import '@vue/runtime-core'` in **global.d.ts** file. | 2023-05-23T19:48:33 | 2023-05-23T19:48:33 | {} | NONE |
vuejs | core | 1,562,226,883 | 8,407 | tjztj | > 我看到它有效，你能提供浏览器版本和更多信息吗？
无效：
Chrome 开发者版
版本 115.0.5773.4（正式版本）dev （64 位）
-------------------------------------------
有效：
Microsoft Edge
版本 115.0.1866.1 (正式版本) dev (64 位) | 2023-05-25T04:01:21 | 2023-05-25T04:02:07 | {} | NONE |
vuejs | core | 1,562,415,426 | 8,407 | sxzz | Relate issue/proposal: https://github.com/w3c/csswg-drafts/issues/6530 | 2023-05-25T07:28:56 | 2023-05-25T07:28:56 | {} | MEMBER |
vuejs | core | 1,563,700,840 | 8,415 | laterdayi | 
| 2023-05-26T01:36:28 | 2023-05-26T01:36:28 | {} | NONE |
vuejs | core | 1,564,430,311 | 8,418 | jd-solanki | After skimming vuetify's code I found that they uses `getCurrentInstance()?.vnode.props` for getting props applied to current component instance. I also implemented POC for anu's global prop defaults.
I just have to run the some piece of code at the start of each SFC.
Closing this as this can be achievable via th... | 2023-05-26T13:53:48 | 2023-05-26T13:53:48 | {} | NONE |
vuejs | core | 1,554,401,173 | 8,310 | rodrigocfd | @pikax thanks for the tip. But since `props.list` is a valid construct, the bug still exists. The issue should be reopened, right? | 2023-05-19T10:59:13 | 2023-05-19T10:59:13 | {} | NONE |
vuejs | core | 1,554,436,103 | 8,352 | pikax | @jd-solanki https://github.com/vuejs/core/pull/8374 fixes the issue | 2023-05-19T11:28:58 | 2023-05-19T11:28:58 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,554,728,978 | 8,376 | ml1nk | I was creating an issue myself, but you were faster. Thanks.
https://stackblitz.com/edit/vitejs-vite-uq3thn?file=src/App.vue
~~~
❯ npm run typecheck
$ vue-tsc --noEmit
src/App.vue:7:10 - error TS2345: Argument of type '{ abcd: string; label: string; }' is not assignable to parameter of type '{ symbol?: any; re... | 2023-05-19T15:06:34 | 2023-05-19T15:06:34 | {} | NONE |
vuejs | core | 1,555,153,889 | 8,214 | leonardorafael | Hi, I made a codepen in vanilla JS and returns null (tested in Chrome).
https://codepen.io/leo-bnu/pen/KKGrXxv
![image](https:... | 2023-05-19T19:46:58 | 2023-05-19T19:50:35 | {} | NONE |
vuejs | core | 1,556,422,603 | 8,375 | mr-pajamas | No intention to close this | 2023-05-22T02:24:27 | 2023-05-22T02:25:47 | {} | NONE |
vuejs | core | 1,557,271,456 | 8,389 | baiwusanyu-c | When there is a mismatch, the hook function is triggered and the parameters `node`, `vnode`, `parentComponent` are passed, but due to the problem caused by the mismatch of the number of nodes(`server rendered element contains fewer child nodes than client vdom` and `server rendered element contains more child nodes th... | 2023-05-22T13:58:49 | 2023-05-22T14:05:00 | {} | MEMBER |
vuejs | core | 1,558,883,984 | 8,388 | hibichann | <script setup lang="jsx">
写上以后babel配置也是不用的 | 2023-05-23T09:17:33 | 2023-05-23T09:17:33 | {} | NONE |
vuejs | core | 1,559,883,120 | 7,629 | fsblemos | This is a problem for component libraries that are used in non TS projects, since after building components don't complain about missing required props. What should I do for consumers to know that there are missing props? | 2023-05-23T17:42:39 | 2023-05-23T17:42:39 | {
"+1": 1
} | NONE |
vuejs | core | 1,561,139,283 | 8,276 | andredewaard | VSCode still throws an typescript error.
vite.config.ts
```typescript
plugins: [
vue({
script: {
defineModel: true
}
})
],
```
package.json
```json
"@vitejs/plugin-vue": "^4.2.3",
"vue": "^3.3.4",
```
Both Volar and Volar (typescript) are on pre release versions
<i... | 2023-05-24T13:21:21 | 2023-05-24T13:21:21 | {
"+1": 1
} | NONE |
vuejs | core | 1,561,889,289 | 7,836 | sto3psl | Hey! Is there anything I can do to get this merged?
It would be so nice to have proper MathML support in a future Vue version. | 2023-05-24T20:32:29 | 2023-05-24T20:32:29 | {} | CONTRIBUTOR |
vuejs | core | 1,564,052,072 | 8,413 | edison1105 | @baiwusanyu-c
uh~ yes. `defineEmits` can't use string as an argument | 2023-05-26T08:57:10 | 2023-05-26T08:57:10 | {} | MEMBER |
vuejs | core | 1,564,610,312 | 8,398 | yyx990803 | I'm sorry, but I'm not sure what you are expecting us to do here.
The warning isn't Vue specific, nor does reproduction show that it is caused by something that should be "fixed" in Vue core. If rendering a huge table causes a reflow, it could theoretically trigger the same warning without Vue involved. I don't see ... | 2023-05-26T16:03:41 | 2023-05-26T16:03:41 | {} | MEMBER |
vuejs | core | 1,556,730,351 | 8,383 | LinusBorg | "Link to reproduction" - you need to provide actual runnable code to for use to reproduce the problem. a snippet to copy and paste is not good enough as we can't be ure to correctly emulate the context you run thi code in. | 2023-05-22T08:02:46 | 2023-05-22T08:02:46 | {} | MEMBER |
vuejs | core | 1,557,173,084 | 7,942 | leonheess | Are you aware of #4404 and https://github.com/EranGrin/vue-web-component-wrapper? | 2023-05-22T12:57:36 | 2023-05-22T12:58:32 | {} | NONE |
vuejs | core | 1,556,982,266 | 7,156 | sxzz | @tjx666 Use `defineOptions` macros and set the `name` property. | 2023-05-22T10:38:59 | 2023-05-22T10:38:59 | {} | MEMBER |
vuejs | core | 1,557,360,339 | 8,316 | MajedMuhammad | I have noticed this bug in the prior few releases:
Then, I updated Vue to the latest `v3.3.4`.
The issue has been resolved, but it causes other issues:
Firefox 71:
![screenshot-console-3](https://github.... | 2023-05-22T14:51:03 | 2023-05-22T14:51:03 | {} | NONE |
vuejs | core | 1,560,243,797 | 6,532 | atlansien | Any progress on this issue? | 2023-05-23T23:12:14 | 2023-05-23T23:12:14 | {
"+1": 5
} | NONE |
vuejs | core | 1,562,408,708 | 8,407 | baiwusanyu-c | This may be a browser problem, Google has modified the default value of `animation-deley` in Chrome canary version | 2023-05-25T07:23:03 | 2023-05-25T07:24:14 | {} | MEMBER |
vuejs | core | 1,562,800,350 | 8,413 | Alfred-Skyblue | [demo](https://play.vuejs.org/#eNp9VM1u2zAMfhXCGJAESORDd/KcIlux0x6h7sG1mcSr/iDJbgvD7z5Klj0lA6ZLwt+P/Eh6zL5rzYYesyIrbWM67cCi6/VjJTuhlXEwgsEzTHA2SsCGXDer6UkJ/fPDoWxtNLM80fm8m2+VbJS0Doaa9whHn237/LKrZJnPgARFgkOhee3QS65MMw8HoVrkhUWOjeuU/IWf9lhlIWGVgbAXkq7IuYJ3ZXhbZZQEyrQUUpT5CpHts7mDg6g1+22VpPZHioEqGmyVFRA0Xkd9eJlAnNO2yPNe6... | 2023-05-25T12:12:54 | 2023-05-25T12:12:54 | {} | MEMBER |
vuejs | core | 1,562,914,363 | 8,373 | Blackfaded | Facing the same issue. Cant type my generic component with
```ts
const contentSwiperRef = ref<InstanceType<typeof ContentSwiper> | null>(null);
```
| 2023-05-25T13:30:45 | 2023-05-25T13:30:45 | {} | NONE |
vuejs | core | 1,558,373,402 | 8,316 | baiwusanyu-c | > I have noticed this bug in the prior few releases: 
>
> Then, I updated Vue to the latest `v3.3.4`. The issue has been resolved, but it causes other issues: Firefox 71: ![screenshot-console... | 2023-05-23T01:47:03 | 2023-05-23T01:47:03 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,558,394,016 | 6,643 | Hccake | same problem | 2023-05-23T02:13:48 | 2023-05-23T02:13:48 | {} | NONE |
vuejs | core | 1,562,920,380 | 8,413 | Alfred-Skyblue | > > [demo](https://play.vuejs.org/#eNp9VM1u2zAMfhXCGJAESORDd/KcIlux0x6h7sG1mcSr/iDJbgvD7z5Klj0lA6ZLwt+P/Eh6zL5rzYYesyIrbWM67cCi6/VjJTuhlXEwgsEzTHA2SsCGXDer6UkJ/fPDoWxtNLM80fm8m2+VbJS0Doaa9whHn237/LKrZJnPgARFgkOhee3QS65MMw8HoVrkhUWOjeuU/IWf9lhlIWGVgbAXkq7IuYJ3ZXhbZZQEyrQUUpT5CpHts7mDg6g1+22VpPZHioEqGmyVFRA0Xkd9eJlAnNO2y... | 2023-05-25T13:34:47 | 2023-05-25T13:34:47 | {} | MEMBER |
vuejs | core | 1,555,044,608 | 8,368 | Boux | @yyx990803 I did a little digging, comparing both vue 3.2 and 3.3's `compileScript` function. Both of them tries to parse the script's content with babel's parser, with a try/catch around it, but in 3.2, the catch simply fails silently and returns the script, and in 3.3 it throws the error
`version 3.2`
https://git... | 2023-05-19T18:05:22 | 2023-05-19T18:05:22 | {
"+1": 2
} | NONE |
vuejs | core | 1,557,643,922 | 7,782 | vis97c | Facing the same issue. When can the fix be review and merged? | 2023-05-22T17:47:37 | 2023-05-22T17:47:37 | {} | NONE |
vuejs | core | 1,560,585,570 | 8,402 | Alfred-Skyblue | There may be some places that need a purer prototype chain, Or should we create literals for some objects we really need?. | 2023-05-24T07:23:08 | 2023-05-24T07:42:13 | {} | MEMBER |
vuejs | core | 1,559,635,888 | 3,399 | extrem7 | The typed directive is a must-have feature after official generic components support.
@yyx990803 Can we expect it in Vue 3.4? | 2023-05-23T15:09:10 | 2023-05-24T08:16:03 | {} | NONE |
vuejs | core | 1,560,961,633 | 8,391 | cschra | Thank you for your answer, but the 'in-dom-template' is a viable feature as per the [official Documentation](https://vuejs.org/guide/essentials/application.html#in-dom-root-component-template)
> Vue will automatically use the container's innerHTML as the template if the root component does not already have a templa... | 2023-05-24T11:40:19 | 2023-05-24T11:40:19 | {} | NONE |
vuejs | core | 1,435,737,813 | 1,503 | choltz | @Nick87-xkk can you describe this more? What did you update to get this working with vue2.7? | 2023-02-18T18:46:59 | 2023-02-18T18:46:59 | {} | NONE |
vuejs | core | 1,435,982,296 | 7,755 | LinusBorg | Concerning the linked comment which essentially is about event bubbling like in normal DOM events: We don't do bubbling because it essentially makes component events share a global namespace, which is not something you want in a component architecture focussed on modularity.
You can work around this i.e. with provid... | 2023-02-19T12:57:43 | 2023-02-19T13:02:30 | {} | MEMBER |
vuejs | core | 1,436,092,356 | 7,719 | MKraust | All listeners are actually props with `on` prefix. For example, `@click` listener becomes `onClick` prop. You can use such props even without using `defineEmits`.
In that case you can do something like this:
```js
const props = defineProps<{
onConfirm: () => void
}>()
const handleConfirm = () => {
if (props.onCon... | 2023-02-19T21:00:51 | 2023-02-19T21:05:38 | {} | NONE |
vuejs | core | 1,436,358,480 | 7,756 | MRezaKarimi | @LinusBorg
So why the Title does not change when I change the route? | 2023-02-20T05:31:25 | 2023-02-20T05:31:25 | {} | NONE |
vuejs | core | 1,436,998,674 | 7,754 | edison1105 | @AlexVagrant
Good catch! PR welcome. | 2023-02-20T13:06:34 | 2023-02-20T13:06:34 | {} | MEMBER |
vuejs | core | 1,438,561,056 | 7,590 | pi0 | Using warning and global setters, i think we will have less issues however:
- We probably need to avoid showing this warning when same version of Vue is from different locations (external util linked from another node_modules directory -- only in development can happen)
- This warning can be false-positive only if ... | 2023-02-21T14:10:48 | 2023-02-21T14:16:24 | {} | NONE |
vuejs | core | 1,439,658,099 | 7,760 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4241071682)
| suite | result |
|-------|--------|
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4241071682/jobs/7370843225) | :white_check_mark: success |
| [pinia](https://github.com/vuejs/ecosystem-ci/actions/runs/42410716... | 2023-02-22T09:05:06 | 2023-02-22T09:10:50 | {} | CONTRIBUTOR |
vuejs | core | 1,440,330,891 | 7,713 | skirtles-code | I think it'd make sense to have a dev warning at runtime if the value passed to `v-bind` isn't an object. | 2023-02-22T16:13:12 | 2023-02-22T16:13:12 | {} | CONTRIBUTOR |
vuejs | core | 1,440,658,052 | 7,746 | sxzz | /ecosystem-ci run | 2023-02-22T19:16:00 | 2023-02-22T19:16:00 | {} | MEMBER |
vuejs | core | 1,434,299,941 | 6,219 | zhoufanglu | > ```js
> const wraper = {
> name: fullPath,
> render() {
> return this.$slots.defaunt();
> }
> }
> ```
这种自定义组件名称的用法哪里有介绍？没见过这种语法 | 2023-02-17T08:36:38 | 2023-02-17T08:37:01 | {} | NONE |
vuejs | core | 1,438,519,900 | 6,692 | skirtles-code | I don't understand this change.
`>>>` won't fail until `2 ^ 32`, which is `4_294_967_296`. The shift is being applied to `start + end`, so the queue itself would need to be half that size to overflow. It doesn't seem realistic for the scheduler queue array to contain 2 billion items. I suspect the browser would cras... | 2023-02-21T13:46:18 | 2023-02-21T13:46:18 | {} | CONTRIBUTOR |
vuejs | core | 1,438,673,465 | 4,294 | demiro | I am having an issue with intersection types....
something like this
```ts
type ButtonProps = {
intent?: IntentType;
size?: SizeType;
} & {
[K in IntentType as `${Lowercase<K>}`]?: boolean;
};
const props = defineProps<ButtonProps>();
```
results in an error
> 13:20:09 [vite] Internal server... | 2023-02-21T15:26:13 | 2023-02-21T16:17:21 | {
"+1": 2
} | NONE |
vuejs | core | 1,438,897,258 | 7,770 | LinusBorg | There's no variable called `cancelIdleCallback` in our codebase. This is a problem with Vuetify using `requestIdleCallback` and Safari/Epiphany having issues with that. | 2023-02-21T18:05:10 | 2023-02-21T18:05:10 | {} | MEMBER |
vuejs | core | 1,438,929,679 | 2,693 | pikax | @yyx990803 Do you mind reviewing this PR?
I need some help on the compiler macro for `defineSlots`, getting `setup-maybe-ref`:
```
- "mySlots": "setup-const",
+ "mySlots": "setup-maybe-ref",
```
and https://github.com/vuejs/core/pull/2693#discussion_r1113433863 | 2023-02-21T18:34:33 | 2023-02-21T18:34:33 | {} | MEMBER |
vuejs | core | 1,439,800,854 | 7,755 | olfek | In Vue 2 this would have been possible by using `this.$on` https://github.com/vuejs/vue/issues/4332#issuecomment-263444492 | 2023-02-22T10:44:36 | 2023-02-22T10:44:36 | {} | NONE |
vuejs | core | 1,435,309,036 | 7,502 | yangwao | Hey, how is this standing? I've heard nuxt-speedkit would need it and then kodadot/nft-gallery is happy to use it 😁 | 2023-02-17T21:43:36 | 2023-02-17T21:43:36 | {
"+1": 1,
"laugh": 2
} | NONE |
vuejs | core | 1,435,980,513 | 7,755 | LinusBorg | The Vue 3 way of doing something like the Dialog example is to use a scoped slot:
https://sfc.vuejs.org/#eNqFkrFu3DAMhl+F1WIH6NnoenCCFEmB7h06VB3ubPpOiSQKknw3GH73UJbjOMmQyfrF3yQ/UqP46Vx1GVDsRRNar1yEgHFwd9Iq48hHGMFjDxP0ngwUbC3W0KM6aDotkarOMmV7s/whgw9k3Gp6vVhsANK2ZEMEE05wm2qVxW/UmuAved19K26kbercGjfFIqJx+hCRFUBz/nE3jvPP... | 2023-02-19T12:49:35 | 2023-02-19T12:54:59 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,436,444,235 | 7,756 | LinusBorg | I just explained that, I think. The computed property never refreshes because `props.number` can't be collected as a dependency - because it's read asynchronously outside the computed's context. so the component always stays the same. | 2023-02-20T07:01:53 | 2023-02-20T07:02:07 | {} | MEMBER |
vuejs | core | 1,438,124,889 | 7,755 | olfek | > I believe @LinusBorg's [solution above](https://github.com/vuejs/core/issues/7755#issuecomment-1435980513) is a more solid pattern for a parent component to expose logic to its slot content (not only in Vue 3 but also in Vue 2).
What if the slot content was not just 1 component, but 20? You would have to repeat yo... | 2023-02-21T09:16:53 | 2023-02-21T09:16:53 | {} | NONE |
vuejs | core | 1,433,095,497 | 7,733 | DrPhil | Similarly, throwing an error in `created` and then also throwing inside `errorCaptured` also leaves `getCurrentInstance` set. You can see this in the same reproducing example. | 2023-02-16T13:33:18 | 2023-02-16T13:33:18 | {} | CONTRIBUTOR |
vuejs | core | 1,433,240,763 | 5,318 | paul-thebaud | Hello, any news on this please? Any schedule fix or work on it?
I'm experiencing the issue with an ORM like library where instances reference each other. | 2023-02-16T15:11:33 | 2023-02-16T15:11:33 | {} | NONE |
vuejs | core | 1,435,500,469 | 7,622 | skirtles-code | I don't think it should matter whether the new job is `pre: true` or not, the insertion point should be the same either way. I think we only need to check the `pre` flag on jobs that are already in the queue.
I believe this change would introduce a regression. The `middle--` part seems unnecessary, and can lead to t... | 2023-02-18T06:41:11 | 2023-02-18T06:41:11 | {} | CONTRIBUTOR |
vuejs | core | 1,435,690,432 | 7,749 | LinusBorg | See: https://github.com/vuejs/language-tools/pull/2417 | 2023-02-18T14:36:05 | 2023-02-18T14:36:05 | {} | MEMBER |
vuejs | core | 1,435,994,698 | 7,755 | olfek | I suppose this would be possible in Vue 3 if `this.$on(...)` still existed | 2023-02-19T13:50:54 | 2023-02-19T13:50:54 | {} | NONE |
vuejs | core | 1,436,211,414 | 7,719 | Autumn-one | > All listeners are actually props with `on` prefix. For example, `@click` listener becomes `onClick` prop. You can use such props even without using `defineEmits`.↳
>
> In that case you can do something like this:↳
>
> ```js
> const props = defineProps<{
> onConfirm: () => void
> }>()
>
> const handleCon... | 2023-02-20T02:23:59 | 2023-02-20T02:23:59 | {} | NONE |
vuejs | core | 1,439,036,676 | 7,755 | olfek | @LinusBorg Why do you say that? Is a `RouterView` like impmentation of `slot` impossible? | 2023-02-21T20:13:09 | 2023-02-21T20:13:09 | {} | NONE |
vuejs | core | 1,440,654,252 | 7,773 | sxzz | Could you please provide more details about this change? Also, the unit tests need to be passed. | 2023-02-22T19:12:42 | 2023-02-22T19:12:42 | {} | MEMBER |
vuejs | core | 1,440,657,812 | 7,748 | sxzz | /ecosystem-ci run | 2023-02-22T19:15:49 | 2023-02-22T19:15:49 | {} | MEMBER |
vuejs | core | 1,435,357,057 | 6,463 | DrJume | The reproduction throws the same error on vue `v3.2.36` | 2023-02-17T22:38:01 | 2023-02-17T22:38:01 | {} | CONTRIBUTOR |
vuejs | core | 1,432,542,607 | 7,657 | hongquan | Reproducible project: https://bitbucket.org/hongquan/vue-wrong-argument-for-use
```console
❯ yarn build
yarn run v1.22.19
$ vue-tsc && vite build
src/main.ts:22:5 - error TS2554: Expected 2 arguments, but got 1.
22 app.use(fluent)
~~~~~~~~~~~
node_modules/@vue/runtime-core/dist/runtime-core.d.ts:... | 2023-02-16T05:32:51 | 2023-02-16T05:32:51 | {} | NONE |
vuejs | core | 1,434,267,687 | 7,568 | yisar | @yyx990803 cc | 2023-02-17T08:02:46 | 2023-02-17T08:02:46 | {} | NONE |
vuejs | core | 1,435,994,454 | 7,755 | olfek | Looks like Angular has this functionality https://stackoverflow.com/a/65294062 | 2023-02-19T13:49:43 | 2023-02-19T13:49:43 | {} | NONE |
vuejs | core | 1,436,363,938 | 7,749 | crystalfp | Fixed by `vue-tsc` new version (1.1.4). Thanks! | 2023-02-20T05:39:17 | 2023-02-20T05:39:17 | {} | NONE |
vuejs | core | 1,436,460,611 | 7,755 | LinusBorg | > I propose the addition of a new <slot-component> that allows the Emit functionality to work as it does with <RouterView />
Not sure how that should work. This should still render slot content, right? so in the following, the listener would be inherited by *All* the children? If so: I'd vote no, we again have unsaf... | 2023-02-20T07:12:10 | 2023-02-20T07:12:10 | {} | MEMBER |
vuejs | core | 1,438,546,138 | 7,590 | yyx990803 | Can you check if f597dc69 + 8d2d5bf4 achieve the same end result in your reproductions?
I wanted to centralize the logic so that the rest of the codebase can forget about this constraint. | 2023-02-21T14:01:23 | 2023-02-21T14:01:23 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,439,052,411 | 7,755 | LinusBorg | I've repeated this a couple times: `RouterView` does not do anything like what you ask. Concerning props and events, all `RouterView` does is this, conceptually:
```js
(props) => h(ComponentForCurrentlyActivePath, props)
```
it passes all attributes and eventlisteners (here represented by `props`) on to that on... | 2023-02-21T20:28:47 | 2023-02-21T20:28:47 | {} | MEMBER |
vuejs | core | 1,439,799,270 | 7,755 | olfek | And if you look at the original issue https://github.com/vuejs/vue/issues/4332
You will see that I am not the only one thinking about this. | 2023-02-22T10:43:19 | 2023-02-22T10:43:19 | {} | NONE |
vuejs | core | 1,432,596,382 | 7,722 | BeADre | @Justineo done | 2023-02-16T06:35:16 | 2023-02-16T06:35:16 | {} | CONTRIBUTOR |
vuejs | core | 1,435,688,885 | 4,836 | defaude | Hey @posva I've shortened the doc blocks a bit, added links to the appropriate docs page where appropriate. What do you think? | 2023-02-18T14:27:54 | 2023-02-18T14:27:54 | {} | CONTRIBUTOR |
vuejs | core | 1,435,692,101 | 7,601 | AlexVagrant | See: https://github.com/vuejs/language-tools/pull/2417 | 2023-02-18T14:46:06 | 2023-02-18T14:46:06 | {} | CONTRIBUTOR |
vuejs | core | 1,435,714,586 | 7,751 | rudyxu1102 | Related to https://github.com/vuejs/vue/issues/12931 | 2023-02-18T16:46:47 | 2023-02-18T16:46:47 | {} | CONTRIBUTOR |
vuejs | core | 1,436,053,576 | 7,756 | LinusBorg | That's expected though. `() => import(componentList|props.number])` will run (and thus, `props.number`will be accessed) when that component is actually being rendered, which happens long after the computed function has run and has collected its dependencies. | 2023-02-19T18:02:11 | 2023-02-19T18:02:11 | {} | MEMBER |
vuejs | core | 1,438,909,371 | 7,755 | olfek | oh sorry I misunderstood, yes if they were in the template we'd have to explicitly set the emit handler, but luckily for us, they could all be grouped in a slot **component** where we could set a shared emit handler. | 2023-02-21T18:15:46 | 2023-02-21T18:15:46 | {} | NONE |
vuejs | core | 1,439,039,001 | 7,755 | olfek | and I mean a new implementation without removing or replacing the current `<slot>` so there are no breaking changes and can be introduced in Vue 3 | 2023-02-21T20:15:21 | 2023-02-21T20:15:21 | {} | NONE |
vuejs | core | 1,439,381,532 | 7,738 | moushicheng | hey ,guys. Forgive me for not reading very understand
your mean
myData.value==Date object when use [type="date"]
and
myData.value=='1702684800000' when use [type="date"] ?
```javascript
// now myData.value==Date object: Wed Feb 15 2023 19:00:00 GMT-0500
<input type="date" v-model.date="myDate"/>... | 2023-02-22T03:18:30 | 2023-02-22T03:18:30 | {} | CONTRIBUTOR |
vuejs | core | 1,439,764,717 | 7,755 | LinusBorg | I don't see what good it does to keep a feature request open when we can say with confidence that this is *not* something we intend to invest any time developing and/or maintaining.
Why can I say that confidently? Because we have discussed and decided against features related to "event bubbling" multiple times in th... | 2023-02-22T10:21:25 | 2023-02-22T10:21:36 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,432,589,009 | 7,729 | LinusBorg | Bug introduced here:
https://github.com/vuejs/core/commit/c513126c5dd12fec1064bf2df53384099f4000d2 | 2023-02-16T06:24:34 | 2023-02-16T06:24:34 | {} | MEMBER |
vuejs | core | 1,432,791,788 | 7,729 | hongquan | This is fluent-vue's bug, so I close this issue. | 2023-02-16T09:37:28 | 2023-02-16T09:37:28 | {} | NONE |
vuejs | core | 1,432,866,197 | 6,504 | MetRonnie | I don't usually add +1 type comments, but I cannot stress enough how difficult it was to debug a problem this behaviour caused, in switching from Vue 2 to 3.
I ended up using `inheritAttrs: false` - https://vuejs.org/guide/components/attrs.html#disabling-attribute-inheritance | 2023-02-16T10:30:36 | 2023-02-16T10:40:16 | {} | NONE |
vuejs | core | 1,435,363,569 | 6,463 | DrJume | I had the same issue inside a Nuxt v3.2.2 app, probably caused by a suspense boundary with async components.
In the following line `prevTree.el` is null, when the error is thrown (`null.parentNode`). Sometimes it is `""`, which does not throw, as `"".parentNode` gives `undefined`, which does not cause any problems.
... | 2023-02-17T22:45:00 | 2023-02-17T22:45:41 | {} | CONTRIBUTOR |
vuejs | core | 1,435,966,883 | 7,622 | edison1105 | @skirtles-code
Thank you for the review and your point is correct.
Close this one. | 2023-02-19T11:49:13 | 2023-02-19T11:49:13 | {} | MEMBER |
vuejs | core | 1,438,905,605 | 7,755 | olfek | > Just like you would do if you had all of these 20 components directly in the template instead of passing them in a slot.
no no, we wouldn't have to
```
<Dialog v-slot="{ onClose }">
<SomeComp1 @done="onClose" />
<SomeComp2 @done="onClose" />
<SomeComp3 @done="onClose" />
...
</Dialog>
```... | 2023-02-21T18:12:19 | 2023-02-21T18:12:19 | {} | NONE |
vuejs | core | 1,432,806,869 | 7,568 | yingpengsha | I need this change, but no one seems to care except us. | 2023-02-16T09:48:41 | 2023-02-16T09:48:41 | {} | NONE |
vuejs | core | 1,433,606,579 | 7,710 | LinusBorg | Have you considered using `expose()`? | 2023-02-16T19:31:01 | 2023-02-16T19:31:01 | {} | MEMBER |
vuejs | core | 1,436,416,874 | 7,696 | JayFate | @sxzz Do you have a minute to review this PR ? | 2023-02-20T06:47:18 | 2023-02-20T06:47:18 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 1,437,996,337 | 7,661 | nestle49 | @yyx990803 Can u comment, please? | 2023-02-21T07:53:21 | 2023-02-21T07:53:21 | {} | NONE |
vuejs | core | 1,438,220,254 | 7,678 | AlexVagrant | @skirtles-code Thanks for your suggestion, I had modified my code, please review it again. Thanks again. | 2023-02-21T10:20:31 | 2023-02-21T10:20:31 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,439,657,593 | 7,760 | sxzz | /ecosystem-ci run | 2023-02-22T09:04:40 | 2023-02-22T09:04:40 | {} | MEMBER |
vuejs | core | 1,439,788,421 | 7,774 | LinusBorg | looks like a duplicate of #6483 | 2023-02-22T10:35:16 | 2023-02-22T10:35:24 | {} | MEMBER |
vuejs | core | 1,436,455,934 | 7,710 | LinusBorg | simplified: setup returns are exposed as part of "this", where also Vue's `_internal` properties live. the objects returned by ?`expose()` doesn't expose internals (its whole point is only to expose what you told it to).
> expose() isn't type safe.
True, would be a better way to fix your issue though if we fix t... | 2023-02-20T07:08:05 | 2023-02-20T07:08:05 | {} | MEMBER |
vuejs | core | 1,439,584,922 | 4,662 | yashwanth2714 | I'm following up on this issue. Do we have an estimated time of completion for the fix? | 2023-02-22T08:06:46 | 2023-02-22T08:06:46 | {
"eyes": 3
} | NONE |
vuejs | core | 1,440,536,831 | 7,738 | thedamon | @moushicheng If i understand your question, yes. The value of the ref is what I'm suggesting could be cast (just like existing v-model modifiers).
I didn't include that in my example because it was in the template scope so it was unwrapped. | 2023-02-22T18:11:25 | 2023-02-22T18:11:25 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.