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 | 755,532,049 | 2,639 | znck | Evan suggested to create an RFC first, I didn't get time to do that. | 2021-01-06T19:07:01 | 2021-01-06T19:07:01 | {} | MEMBER |
vuejs | core | 755,815,826 | 2,956 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2021-01-07T00:58:24 | 2021-01-07T00:58:24 | {} | CONTRIBUTOR |
vuejs | core | 756,703,837 | 2,969 | pdanpdan | Yes, the equivalent of `hook:created/mounted/...` would be nice also, but they would need a payload that specifies which component is processed (the main component or the placeholder/loading or error one) | 2021-01-08T11:22:22 | 2021-01-08T11:22:42 | {} | NONE |
vuejs | core | 758,432,728 | 2,990 | HcySunYang | The template refs are set in the order of patching, not in the order of the DOM structure. For your demo, you can use an object instead of an array to achieve the goal: https://codesandbox.io/s/ref-dom-forked-p493e?file=/src/App.vue | 2021-01-12T06:18:29 | 2021-01-12T06:18:29 | {} | MEMBER |
vuejs | core | 759,108,017 | 2,783 | JerryWu1234 | > As a workaround, you can use a custom directive to get the element of the inner vNode (you need to write render function if it is a slot).
>
> ```js
> // using render function
> import { withDirectives, h, Teleport } from 'vue'
>
> const dir = {
> mounted (el) {
> console.log(el)
> },
> updated ... | 2021-01-12T23:44:08 | 2021-01-12T23:44:08 | {} | NONE |
vuejs | core | 755,272,881 | 2,944 | edison1105 | > like checking for valid JS syntax, etc.
I also thought of this and I found a library to check js syntax:https://github.com/jquery/esprima.
maybe you can get some inspiration from this library.
| 2021-01-06T12:30:45 | 2021-01-06T12:30:45 | {} | MEMBER |
vuejs | core | 756,645,808 | 2,835 | HcySunYang | This makes it work:
```css
&__item, ::v-slotted(&__item) {
margin: 0 15px;
a {
color: #4CAF50;
}
}
```
https://codesandbox.io/s/vue3-component-scoped-scss-forked-1urfp?file=/src/components/MainMenu.vue | 2021-01-08T09:20:06 | 2021-01-08T09:20:06 | {} | MEMBER |
vuejs | core | 756,688,198 | 2,969 | LinusBorg | Can you give us a brief example of a specific use case? that would help understand the challenge better. | 2021-01-08T10:47:09 | 2021-01-08T10:47:09 | {
"+1": 1
} | MEMBER |
vuejs | core | 757,461,013 | 2,380 | jods4 | @LinusBorg
> But thinking about it, one could argue that it should traverse them as a raw object could still contain nested reactive objects.
That's exactly what I would argue.
I may create a `shallowReactive` array because I don't want to deeply proxify everything that is in it.
It doesn't mean that the objec... | 2021-01-10T11:34:15 | 2021-01-10T11:34:15 | {} | CONTRIBUTOR |
vuejs | core | 757,480,819 | 2,944 | glen-84 | That's essentially what I suggested [above](https://github.com/vuejs/vue-next/issues/2944#issuecomment-755250639), although I wasn't aware that the compiler already included Babel, which makes this even more feasible. It's probably worth reconsidering. | 2021-01-10T13:59:11 | 2021-01-10T13:59:11 | {} | NONE |
vuejs | core | 756,705,756 | 2,969 | pdanpdan | At a framework level (quasar) we can receive custom components to be used for dialogs. The components have an interface that requires them to have a show method, but the component can be sync it async. When the wrapper dialog is mounted it tries to call the show method of the custom component, but it should do so once ... | 2021-01-08T11:27:01 | 2021-01-08T11:32:31 | {} | NONE |
vuejs | core | 757,648,049 | 2,710 | antfu | @knightly-bot build this | 2021-01-11T06:18:59 | 2021-01-11T06:18:59 | {} | MEMBER |
vuejs | core | 757,762,295 | 2,973 | posva | You are right, I missed the names! A new issue with a proper repro like the other one is still preferred, thanks! | 2021-01-11T09:05:37 | 2021-01-11T09:05:37 | {} | MEMBER |
vuejs | core | 759,311,381 | 2,998 | delowardev | @edison1105 Thanks for the Information. | 2021-01-13T09:08:44 | 2021-01-13T09:08:44 | {} | NONE |
vuejs | core | 759,347,712 | 2,995 | martinsura | `h` works.
Not sure if ths is bug, but closing. Thanks for the help | 2021-01-13T10:12:12 | 2021-01-13T10:12:12 | {} | NONE |
vuejs | core | 757,713,813 | 2,985 | LinusBorg | https://github.com/mmd0308/hzqing-vue-timeline/blob/master/package.json#L18
This library is not Vue 3 compatible. | 2021-01-11T08:30:58 | 2021-01-11T08:30:58 | {} | MEMBER |
vuejs | core | 755,815,605 | 2,951 | lijingfaatcumt | > The use of that piece of code is explained in the comment directly above it.
i think the code above i mentinoned is useless, because in function createReactiveObject will solve the situation that if trying to observe a readonly proxy, return the readonly version, becasuse in createReactiveObject , except readonly(... | 2021-01-07T00:57:35 | 2021-01-07T00:57:35 | {} | NONE |
vuejs | core | 756,000,382 | 2,961 | jw-foss | @posva I understand that this is duplicated, but this bug is considered `p4 - important` right? I dunno how you guys manages the priority, but IMHO this bug can be critical though. We all know `3.0.3` worked fine but `3.0.3` has bugs as well... | 2021-01-07T09:34:58 | 2021-01-07T09:34:58 | {} | NONE |
vuejs | core | 758,647,098 | 2,944 | znck | > So I could write TS in an expression but it wouldn't be compiled by the tsc compiler I used, types would be stripped off by babel?
VueDX/TS Plugin (theoretically) supports type checking in template expressions (though it is not covered by tests because nobody asked for it).
> But does that even work with tooli... | 2021-01-12T13:13:56 | 2021-01-12T13:14:04 | {} | MEMBER |
vuejs | core | 758,774,966 | 2,993 | LinusBorg | you can also define `click` as a component event by adding
```js
export default {
emits: ["click"],
}
```
With this, Vue will no longer add a native eventlistener for this event, and you can control it with `$emit` | 2021-01-12T16:28:54 | 2021-01-12T16:28:54 | {} | MEMBER |
vuejs | core | 755,203,827 | 2,870 | LinusBorg | @underfin is this ready to be approved? | 2021-01-06T09:59:38 | 2021-01-06T09:59:44 | {} | MEMBER |
vuejs | core | 756,599,681 | 2,966 | HcySunYang | See https://v3.vuejs.org/guide/component-attrs.html#attribute-inheritance | 2021-01-08T07:31:42 | 2021-01-08T07:31:42 | {} | MEMBER |
vuejs | core | 756,482,164 | 2,957 | lijingfaatcumt | > If you are submitting a fix, can you add a test that failed before and now passes
@posva i only find 4 line code that i think they are useless, and i want to delete them, and when i delete them and run 'npm test', there are no errors, so i pull this request, then reason i think useless is bellow
```javascript
if... | 2021-01-08T01:06:23 | 2021-01-08T09:43:05 | {} | NONE |
vuejs | core | 757,218,888 | 2,972 | Aubyn | Thanks, I'll use `assignment 1` now, as it meets logical concerns of Composition API in `<script setup>` and perform expectedly. | 2021-01-09T13:58:44 | 2021-01-09T13:59:13 | {} | NONE |
vuejs | core | 758,597,861 | 2,944 | znck | > expressions in template can only be JS, no other language allowed.
compiler allows additional plugins for JS expression parsing, so you can use any language supported by `@babel/parser` (TypeScript and Flow are supported).
> compiler-sfc already embeds a JS parser, namely Babel.
babel is only used in AOT com... | 2021-01-12T11:35:32 | 2021-01-12T11:35:32 | {} | MEMBER |
vuejs | core | 759,109,058 | 2,783 | JerryWu1234 | > > As a workaround, you can use a custom directive to get the element of the inner vNode (you need to write render function if it is a slot).
> > ```js
> > // using render function
> > import { withDirectives, h, Teleport } from 'vue'
> >
> > const dir = {
> > mounted (el) {
> > console.log(el)
> > },... | 2021-01-12T23:46:58 | 2021-01-12T23:46:58 | {} | NONE |
vuejs | core | 759,309,169 | 2,998 | edison1105 | see https://developer.mozilla.org/en-US/docs/Web/CSS/color
> If the value is translucent, the computed value will be the rgba() corresponding one. If it isn't, it will be the rgb() corresponding one. The transparent keyword maps to rgba(0,0,0,0).
Meaning that no matter what is your input, the computed value alway... | 2021-01-13T09:04:54 | 2021-01-13T09:04:54 | {} | MEMBER |
vuejs | core | 759,392,887 | 3,000 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/2474 | 2021-01-13T11:38:49 | 2021-01-13T11:38:49 | {
"+1": 1
} | MEMBER |
vuejs | core | 759,396,405 | 2,994 | posva | > This is confusing as developers can access methods on regular HTML elements and non-wrapper Vue components without $el.
It's a feature though, as accessing the component is often really useful. It's easy to write a function that unwraps the `$el` property:
```js
function unwrapElement(el) {
el = unref(el)
... | 2021-01-13T11:46:02 | 2021-01-13T11:46:17 | {} | MEMBER |
vuejs | core | 755,816,492 | 2,956 | lijingfaatcumt | > Hello, thank you for taking time filling this issue!
>
> However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been au... | 2021-01-07T01:00:29 | 2021-01-07T01:00:29 | {} | NONE |
vuejs | core | 755,918,566 | 2,960 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2021-01-07T06:36:57 | 2021-01-07T06:36:57 | {} | NONE |
vuejs | core | 755,956,792 | 2,961 | jw-foss | After I took a look at the issue #2757 , I went to inspect code for `vShow` and added a `debugger` for `update` method, I found that `update` gets called 3 times for a single call (maybe because the update for the component children triggered the following call). | 2021-01-07T08:08:42 | 2021-01-07T08:08:42 | {} | NONE |
vuejs | core | 756,687,034 | 2,968 | HcySunYang | Please submit this issue to `element-plus` first, I tried to read its source code, but it is really huge. I tried to use the following simple component instead of `el-column`, and it could not be reproduced. I think you should give a clean reproduction. If this issue only occurs in a specific environment (e.g. element-... | 2021-01-08T10:44:23 | 2021-01-08T10:44:23 | {} | MEMBER |
vuejs | core | 757,461,692 | 1,347 | jods4 | @yyx990803 Friendly ping here.
I agree that error handling is one thing that must be polished before Suspense can leave its Experimental status.
But since I opened this issue in June 2020, there has been no public activity on this topic.
Do you have any ETA or plan to communicate about Suspense?
It was a much t... | 2021-01-10T11:40:05 | 2021-01-10T11:40:05 | {
"+1": 11
} | CONTRIBUTOR |
vuejs | core | 757,461,955 | 2,380 | jacekkarczmarczyk | should there be `markRaw` and `markDeepRaw` or `markRaw(object, { deep: bool })`? | 2021-01-10T11:41:55 | 2021-01-10T11:41:55 | {} | CONTRIBUTOR |
vuejs | core | 757,761,344 | 2,973 | jods4 | Yes, those are 2 different issues.
I'll reopen this one if I manage to create a minimal repro. | 2021-01-11T09:04:41 | 2021-01-11T09:04:41 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 757,763,548 | 2,977 | posva | Para hacer preguntas utiliza [StackOverflow](http://stackoverflow.com/tags/vue.js) o el [Discord](https://vue-land.js.org/)
Los bug reports deben tener una repro minima como explicado en https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro | 2021-01-11T09:07:17 | 2021-01-11T09:07:17 | {} | MEMBER |
vuejs | core | 758,440,658 | 2,992 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2021-01-12T06:37:41 | 2021-01-12T06:37:41 | {} | NONE |
vuejs | core | 758,445,133 | 2,990 | Iroha1024 | @HcySunYang thanks | 2021-01-12T06:47:47 | 2021-01-12T06:47:47 | {} | NONE |
vuejs | core | 763,389,995 | 3,040 | skirtles-code | It looks like `callHookFromExtends` and `callHookFromMixins` are essentially the same function, except for the loop.
Should they maybe be refactored so that the core logic isn't duplicated? | 2021-01-20T07:11:23 | 2021-01-20T07:11:23 | {} | CONTRIBUTOR |
vuejs | core | 763,488,889 | 3,059 | pgy108103 | see that
https://github.com/pgy108103/vue3_vite_issue_sample/blob/ref_sugar_watch_issue/src/App.vue
| 2021-01-20T10:03:10 | 2021-01-20T10:04:42 | {} | NONE |
vuejs | core | 764,608,321 | 3,079 | edison1105 | > if the code is being refactored there must be a test case that was failing before
makes sense, I added the test cases | 2021-01-21T12:25:02 | 2021-01-21T12:25:02 | {} | MEMBER |
vuejs | core | 766,407,491 | 2,602 | jaspertey | From what I gather, the `<template comments>` capability is not supported in Vue 3 SFCs? Is there any workaround available? In my case, the HTML comments are being stripped out only in production mode, and I'm confused where the root cause of the behaviour lies; my webpack config, the internal behaviour of @vue/compile... | 2021-01-24T18:22:15 | 2021-01-24T18:22:15 | {} | NONE |
vuejs | core | 767,492,153 | 3,099 | LinusBorg | in the `unmounted` stage, effects have been stopped, and stopped effects (if using a scheduler) return `undefined`:
https://github.com/vuejs/vue-next/blob/7f086369003b50101849f4bcb8dd2978c1ea87ff/packages/reactivity/src/effect.ts#L86-L88
In that sense, it's expected.
But if we don't want this behaviour for `c... | 2021-01-26T11:49:57 | 2021-01-26T11:49:57 | {} | MEMBER |
vuejs | core | 763,618,660 | 3,071 | posva | do you have a reproduction or a failing test case? | 2021-01-20T13:51:35 | 2021-01-20T13:51:35 | {} | MEMBER |
vuejs | core | 763,678,296 | 3,071 | clarkdo | Not actually, I just happened to read this code while testing, I don't think `hasDynamicSlots` should be true if slotName is empty and I didn't find any evidence that `slotName` couldn't be empty either, it `slotName` must be not empty, I think we can remove `default` assignment. | 2021-01-20T14:58:09 | 2021-01-20T14:58:09 | {} | CONTRIBUTOR |
vuejs | core | 764,411,941 | 3,076 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2021-01-21T06:26:24 | 2021-01-21T06:26:24 | {} | NONE |
vuejs | core | 764,453,217 | 3,077 | 07akioni | > I think `props` is data verification, but not type detection ...
The verification is inconsistent in different prop format with actually the same behavior. | 2021-01-21T07:56:46 | 2021-01-21T07:56:46 | {} | CONTRIBUTOR |
vuejs | core | 765,148,211 | 3,081 | yangdan8 | ```javascript
import { defineComponent, PropType } from 'vue';
function stringOnly(v: string) {}
defineComponent({
name: 'PropsTest',
props: {
a: String,
a1: String as PropType<string>,
b: {
type: String,
default: undefined,
},
b1: {
type: String as PropType<... | 2021-01-22T05:56:05 | 2021-01-22T05:56:05 | {} | CONTRIBUTOR |
vuejs | core | 765,292,833 | 2,851 | lijingfaatcumt | > > second we can pass arount the readonly by function toRaw and reactive and then operate the origin object, so the problem you said i pass around the readonly is has existing
>
> That's _explicitly_ doing hacky stuff. If you really need / want to, it's fine.
>
> The problem is that `reactive` is _implicitly_ ca... | 2021-01-22T10:05:14 | 2021-01-22T10:16:23 | {} | NONE |
vuejs | core | 766,589,547 | 3,091 | HcySunYang | This issue has the same reason as https://github.com/vuejs/vue-next/issues/3072, and will be fixed in https://github.com/vuejs/vue-next/pull/3080 | 2021-01-25T06:51:29 | 2021-01-25T06:51:29 | {} | MEMBER |
vuejs | core | 766,638,163 | 3,090 | LinusBorg | Just to add: it doesn't make too much sense to compare performance in development mode (`npm run serve`). Vue 3 could very well be a tad slower as Vue 2, but that would not matter unless it was so bad that it slowed down your development work, which it isn't.
What's important is the production build. | 2021-01-25T08:20:52 | 2021-01-25T08:20:52 | {} | MEMBER |
vuejs | core | 766,715,588 | 1,696 | ianef | @Timmitry, many thanks for this. I had thought of something similar. It's a shame we are going to have to litter our code base with totally unnecessary code. We are facing a lot of work to update all the main application hook points in all our projects. I might try and push for an RFC to create a new lifecycle hook, s... | 2021-01-25T10:27:24 | 2021-01-25T10:27:24 | {} | NONE |
vuejs | core | 763,480,935 | 3,059 | xlboy | do you mean [#3068](https://github.com/vuejs/vue-next/issues/3068)? | 2021-01-20T09:50:25 | 2021-01-20T09:50:25 | {
"+1": 1,
"laugh": 2
} | NONE |
vuejs | core | 763,513,617 | 3,068 | posva | Seems to be a regression of https://github.com/vuejs/vue-next/issues/2231 | 2021-01-20T10:43:27 | 2021-01-20T10:43:27 | {
"+1": 2
} | MEMBER |
vuejs | core | 764,452,206 | 3,077 | Kingbultsea | I think `props` is data verification, but not type detection ... | 2021-01-21T07:54:31 | 2021-01-21T07:54:31 | {} | CONTRIBUTOR |
vuejs | core | 764,462,580 | 3,078 | showyoulove | So... this is a bug? I see something about duplicatekey in commits.
> There is no code in your reproduction link
You can try it by yourself! | 2021-01-21T08:15:44 | 2021-01-21T08:15:44 | {} | NONE |
vuejs | core | 767,288,399 | 3,097 | HcySunYang | This caused by [jsx-next](https://github.com/vuejs/jsx-next), you should submit the issue there.
BTW: The reason for it is that the child nodes of `keepAlive` are transformed to slots, which is wrong, it should be treated as the children as it is. | 2021-01-26T04:27:47 | 2021-01-26T04:27:47 | {
"+1": 2
} | MEMBER |
vuejs | core | 767,498,109 | 3,099 | kiaking | Yeah that's true. Getting back cached computed value sounds right. I think this is tiny issue not sure if it's worth doing something about it, but I can understand it could be confusing because if the computed is accessed once, it looks like `computed` is working inside `unmounted` hook... maybe we should document it a... | 2021-01-26T12:02:17 | 2021-01-26T12:02:17 | {} | MEMBER |
vuejs | core | 767,555,330 | 3,095 | eczn | #2164 just resolves component's inner type inference but no TSX attr inference.
if we want to resolve it, we must to do some change to `global JSX namespace`, and use some feature of it to resovle this. | 2021-01-26T13:53:53 | 2021-01-26T13:54:05 | {} | NONE |
vuejs | core | 763,403,762 | 2,851 | jods4 | @lijingfaatcumt Not having 2 distinct instances for the same object is good, but I still have concerns with the concept of having both a deep and a shallow versions of the same object graph and all the unexpected behaviours it leads to.
It will unwillingly lead to having both raw and reactive versions of instances d... | 2021-01-20T07:41:04 | 2021-01-20T07:41:04 | {} | CONTRIBUTOR |
vuejs | core | 763,440,144 | 3,067 | LadyYang | When the component is updated,n1 is not equal to n2 | 2021-01-20T08:50:38 | 2021-01-20T08:50:38 | {} | NONE |
vuejs | core | 763,478,283 | 3,066 | Kingbultsea | > fix: #3068
> fix: #3059 | 2021-01-20T09:46:14 | 2021-01-20T09:46:14 | {} | CONTRIBUTOR |
vuejs | core | 764,189,182 | 3,073 | Kingbultsea | 
| 2021-01-21T02:25:27 | 2021-01-21T02:25:27 | {} | CONTRIBUTOR |
vuejs | core | 766,408,899 | 2,221 | jaspertey | > By default, comments are not kept in production, but you can achieve this by providing the `comments: true` option to the compiler
Where exactly do I specify this `comments: true` option? Somewhere within my package.json? Within my webpack config "vue-loader" options? Or somewhere else? | 2021-01-24T18:31:50 | 2021-01-24T18:32:15 | {} | NONE |
vuejs | core | 766,765,978 | 1,696 | ianef | @Timmitry I reworked your example a little to only include attributes prefixed with 'data-' and also remove them from the attributes list when parsed. Processing the list in reverse allows the attribute to be deleted without messing up the loop processing.
```javascript
// Convert the attributes of the given html e... | 2021-01-25T11:57:42 | 2021-01-26T12:08:36 | {
"+1": 1
} | NONE |
vuejs | core | 763,441,904 | 3,001 | skirtles-code | This problem manifests itself in other ways too. e.g.:
```html
<button v-if="a <b && b > 7">Click</button>
````
The missing space character after the `<` leads to it being treated as a tag inside `decodeHtmlBrowser` and compilation fails. Obviously it's trivial to workaround it in this case by adding a space.
... | 2021-01-20T08:53:52 | 2021-01-20T08:53:52 | {} | CONTRIBUTOR |
vuejs | core | 763,452,405 | 3,067 | Kingbultsea | > When the component is updated,n1 is not equal to n2
reference | 2021-01-20T09:05:59 | 2021-01-20T09:05:59 | {
"-1": 1
} | CONTRIBUTOR |
vuejs | core | 764,464,897 | 3,078 | HcySunYang | The link you provided is just empty, please provide a valid reproduction and write the steps in English(so more people can help you), otherwise I will close this issue | 2021-01-21T08:20:25 | 2021-01-21T08:20:25 | {} | MEMBER |
vuejs | core | 765,224,607 | 2,851 | jods4 | > second we can pass arount the readonly by function toRaw and reactive and then operate the origin object, so the problem you said i pass around the readonly is has existing
That's _explicitly_ doing hacky stuff. If you really need / want to, it's fine.
The problem is that `reactive` is _implicitly_ called on ev... | 2021-01-22T08:15:23 | 2021-01-22T08:15:23 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 767,363,944 | 3,095 | pikax | I'm working on something very similar (https://github.com/vuejs/vue-next/pull/2164) but for the `defineComponent` and `h`, but sure if that would translate for the TSX | 2021-01-26T07:43:04 | 2021-01-26T07:43:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 767,372,926 | 3,095 | eczn | > I'm working on something very similar (#2164) but for the `defineComponent` and `h`, but sure if that would translate for the TSX
u mean u are not sure that it can map vue emit name `XXX` to JSX attr `onXXX={xxx}` ? | 2021-01-26T08:03:44 | 2021-01-26T08:03:44 | {} | NONE |
vuejs | core | 767,387,274 | 3,095 | pikax | > u mean u are not sure that it can map vue emit name `XXX` to JSX attr `onXXX={xxx}` ?
No, I meant if the https://github.com/vuejs/vue-next/pull/2164 would work on TSX (I just tested and it doesn't)
We should be using a very similar approach not sure if we can reuse the same types, the types I created are [here... | 2021-01-26T08:33:01 | 2021-01-26T08:33:01 | {} | MEMBER |
vuejs | core | 768,020,965 | 3,107 | xiachaoxulu | edit | 2021-01-27T04:31:10 | 2021-01-27T04:31:10 | {} | NONE |
vuejs | core | 763,452,239 | 3,065 | jods4 | https://github.com/vuejs/rfcs/discussions/256 | 2021-01-20T09:05:44 | 2021-01-20T09:05:44 | {} | CONTRIBUTOR |
vuejs | core | 764,574,717 | 3,074 | posva | I see, I think that piece of code deserves a comment explaining why it's done as reading it doesn't explain why there is a different piece of code in dev and propd | 2021-01-21T11:26:40 | 2021-01-21T11:26:40 | {} | MEMBER |
vuejs | core | 765,087,436 | 2,851 | lijingfaatcumt | > @lijingfaatcumt `reactive` returns a readonly version if its input is readonly and that's not something you can remove! I see you've changed the test for that in your PR but it's wrong.
>
> If some code hands you out a readonly object, you should not get around it and start modifying it. If you do so you break the... | 2021-01-22T03:01:14 | 2021-01-22T03:01:14 | {} | NONE |
vuejs | core | 765,238,459 | 3,079 | Mr14huashao | If you can, please rebase your code in your PR, which helps us understand your solution.
Thanks ^_^
| 2021-01-22T08:40:06 | 2021-01-22T08:40:06 | {} | NONE |
vuejs | core | 766,631,138 | 3,090 | posva | Tested with a project using vite and vue 3 and then the same components using vue-cli with vue 2, after bundling in prod mode.
Vue 3
Vue 2
>
> Vue 2
> ![vue 2](https://user-images.githubuserconten... | 2021-01-26T08:15:44 | 2021-01-26T08:15:44 | {} | NONE |
vuejs | core | 764,618,811 | 3,074 | HcySunYang | Aha sure, added... | 2021-01-21T12:45:16 | 2021-01-21T12:45:16 | {} | MEMBER |
vuejs | core | 764,715,368 | 3,050 | Xenoha | Hello @HcySunYang , any update on the above? | 2021-01-21T15:18:58 | 2021-01-21T15:18:58 | {} | NONE |
vuejs | core | 764,909,489 | 2,841 | toams69 | What is the state of this PR ?
I am facing the same issue using vue 3.0.5.
I can't catch event from webcomponent having a dash as name.
Even if I am using camelcase instead of keba case | 2021-01-21T20:15:01 | 2021-01-21T20:15:01 | {
"+1": 1
} | NONE |
vuejs | core | 765,656,852 | 3,086 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2021-01-22T20:10:49 | 2021-01-22T20:10:49 | {} | CONTRIBUTOR |
vuejs | core | 767,279,229 | 3,095 | HcySunYang | Has @pikax ever worked for this? maybe @pikax can give https://github.com/vuejs/vue-next/pull/3096 a review. I think it may not be necessary to use `LibraryManagedAttributes`? because it can work like props | 2021-01-26T03:54:30 | 2021-01-26T03:54:56 | {} | MEMBER |
vuejs | core | 767,323,954 | 3,098 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2021-01-26T06:22:43 | 2021-01-26T06:22:43 | {} | NONE |
vuejs | core | 768,101,516 | 3,108 | 07akioni | 
You've missed `,` before `setup ()`.
It does work.
| 2021-01-27T07:46:30 | 2021-01-27T07:46:30 | {} | CONTRIBUTOR |
vuejs | core | 763,389,361 | 3,061 | wenfangdu | Yes, forgot the good old `inheritAttrs`, thanks! | 2021-01-20T07:09:59 | 2021-01-20T07:09:59 | {} | NONE |
vuejs | core | 763,452,332 | 3,067 | posva | You shouldn't rely on `__vnode` as it's internal | 2021-01-20T09:05:53 | 2021-01-20T09:05:53 | {} | MEMBER |
vuejs | core | 764,467,111 | 2,851 | jods4 | @lijingfaatcumt `reactive` returns a readonly version if its input is readonly and that's not something you can remove! I see you've changed the test for that in your PR but it's wrong.
If some code hands you out a readonly object, you should not get around it and start modifying it. If you do so you break the contr... | 2021-01-21T08:24:44 | 2021-01-21T08:24:44 | {} | CONTRIBUTOR |
vuejs | core | 764,570,949 | 3,074 | HcySunYang | Yeah, it's only occurs in dev | 2021-01-21T11:20:37 | 2021-01-21T11:20:37 | {} | MEMBER |
vuejs | core | 767,576,926 | 3,077 | 07akioni | > I think this is the right way to identify the type:
>
> Format Expected Prop Type Current Behavior
> 1 name: String string | undefined ✅
> 2 name: String as PropType X | undefined ✅
> 3 name: { type: String, default: undefined } string | undefined string
> 4 name: { type: String as PropType, default: undefined... | 2021-01-26T14:27:35 | 2021-01-26T14:27:44 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 764,441,042 | 3,078 | Kingbultsea | There is no code in your reproduction link | 2021-01-21T07:28:36 | 2021-01-21T07:28:36 | {} | CONTRIBUTOR |
vuejs | core | 764,510,035 | 3,078 | posva | @showyoulove we expect bug reports to contain valid reproductions: https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro | 2021-01-21T09:40:48 | 2021-01-21T09:40:48 | {} | MEMBER |
vuejs | core | 765,805,232 | 3,087 | edison1105 | ur reproduction link show empty | 2021-01-23T00:59:38 | 2021-01-23T00:59:38 | {} | MEMBER |
vuejs | core | 766,580,762 | 3,093 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 40.51 KB (+0.01% 🔺) |
| runtime-dom.global.prod.js | 26.83 KB (-0.01% 🔽) |
| size-check.global.prod.js | 16.21 KB (-0.02% 🔽) | | 2021-01-25T06:33:37 | 2021-01-25T06:33:37 | {} | NONE |
vuejs | core | 766,590,367 | 2,878 | peter50216 | Gentle ping on this | 2021-01-25T06:52:58 | 2021-01-25T06:52:58 | {} | NONE |
vuejs | core | 766,726,477 | 1,696 | Timmitry | @ianef Glad I could help 😊
> I tend to use specific parsing for each attribute as they can often get parsed as the wrong type for String, Number, Boolean etc. That way I can be more specific about the prop types in the component.
We have Ruby on Rails as backend, and just call `.to_json` when setting the html-a... | 2021-01-25T10:45:39 | 2021-01-25T10:45:39 | {} | NONE |
vuejs | core | 767,341,800 | 3,077 | yangdan8 | I think this is the right way to identify the type:
| | Format | Expected Prop Type | Current Behavior |
| ---- | ----------------------------------------------------------- | -------------------- | ---------------- |
| 1 | name: String ... | 2021-01-26T06:50:22 | 2021-01-26T06:50:22 | {} | CONTRIBUTOR |
vuejs | core | 767,655,615 | 3,103 | posva | Props are correctly inferred:
```js
props: { message: String }
```
will produce a property `message` with type `string | undefined`. If you found a breaking scenario please provide a reproduction in a new issue | 2021-01-26T16:18:21 | 2021-01-26T16:18:21 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.