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 | 751,849,702 | 2,898 | posva | This won't be possible, at least inside Vue. Maybe in a VSCode plugin, but you should open an issue on the plugins repo (Vetur Vue dx).
The type should be added where the `any` is at ` @Prop({ default: () => [] }) private rows!: Array<any>;` | 2020-12-28T20:12:09 | 2020-12-28T20:12:09 | {} | MEMBER |
vuejs | core | 751,852,807 | 2,897 | Revyn112 | Found something interesting here on CEF issue tracker: https://bitbucket.org/chromiumembedded/cef/issues/2749/osr-results-in-weird-eventtimestamp-values | 2020-12-28T20:22:44 | 2020-12-28T20:22:44 | {} | NONE |
vuejs | core | 749,073,134 | 2,858 | 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%) | | 2020-12-21T16:48:12 | 2020-12-21T16:48:12 | {} | NONE |
vuejs | core | 749,488,227 | 2,094 | LinusBorg | @wonderful-panda I see you started working on this in your fork. Do you need any help to get this ready for a PR? | 2020-12-22T11:12:45 | 2020-12-22T11:12:45 | {} | MEMBER |
vuejs | core | 751,395,783 | 2,849 | LinusBorg | agreed. I sent a seperate PR for the textarea thing. This one here is again good to go. | 2020-12-26T21:01:41 | 2020-12-26T21:01:41 | {} | MEMBER |
vuejs | core | 748,523,801 | 2,851 | LinusBorg | Ah dang, it seems I had the sort-imports extension active involuntarily. That's why there a bunch of changes to the import statementsnthat are unnecessary.
Let me know wether I should revert those. | 2020-12-19T20:57:21 | 2020-12-19T20:57:21 | {} | MEMBER |
vuejs | core | 748,584,376 | 2,853 | posva | The argument is what goes after the `:`, `v-mydirective:foo` `foo` is the argument. The typings are correct.
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! Also don't open issues with invalid or incomplete reproductions (https://new-issue.vuej... | 2020-12-20T09:33:27 | 2020-12-20T09:33:46 | {} | MEMBER |
vuejs | core | 749,040,108 | 2,775 | nonnorm | I'm having the same problem, but with `data` instead of `props`. I don't have any validators or anything like that, and it works just fine when using javascript.
```vue
<script lang="ts">
export default {
data() {
return {
platform: "x86_64"
};
},
computed: {
showMachines() {
r... | 2020-12-21T15:44:15 | 2020-12-21T15:48:19 | {} | NONE |
vuejs | core | 749,485,381 | 2,863 | posva | As a workaround you can specify the component options object instead of its name:
```js
setup() {
return {
view: MyTest,
}
},
``` | 2020-12-22T11:05:45 | 2020-12-22T11:05:45 | {} | MEMBER |
vuejs | core | 750,801,143 | 2,877 | edison1105 | maybe close by #2717, its not release yet. | 2020-12-24T08:17:29 | 2020-12-24T08:44:21 | {} | MEMBER |
vuejs | core | 751,198,928 | 2,882 | lgz5689 | >
>
> You overwirte the value at here https://gitee.com/liguangzheng777/school/blob/master/src/views/student/add.vue#L97
in 97 overwirte console error:Uncaught (in promise) TypeError: oldChildren is null
I attempt shield https://gitee.com/liguangzheng777/school/blob/master/src/views/student/add.vue#L26 code suc... | 2020-12-25T07:39:49 | 2020-12-25T07:39:49 | {} | NONE |
vuejs | core | 751,239,044 | 2,883 | edison1105 | you should :
``` javascript
const obj = reactive({
reason: '',
sellChannel: [1, 2],
})
``` | 2020-12-25T11:56:57 | 2020-12-25T11:56:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 748,826,303 | 2,854 | LinusBorg | Please follow the issue guidelines and provide a description and reproduction code. | 2020-12-21T07:54:51 | 2020-12-21T07:54:51 | {} | MEMBER |
vuejs | core | 749,625,812 | 2,865 | yyyanghj | Duplicate of #2715 | 2020-12-22T16:12:56 | 2020-12-22T16:12:56 | {} | CONTRIBUTOR |
vuejs | core | 751,402,619 | 2,889 | tabjy | Took a deeper look in the source. [`render.ts`](https://github.com/vuejs/vue-next/blob/8ac2241b224aec73707e8f2b5c2a2c7b8b7259a4/packages/server-renderer/src/render.ts#L88) doesn't really check if there is any `serverPrefetch` defined in mixins. Is this an intentional design? It seems to be supported in [vue 2](https://... | 2020-12-26T22:31:02 | 2020-12-26T22:31:02 | {} | NONE |
vuejs | core | 751,887,546 | 2,899 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js).
---
Read https://new-issue.vuejs.org/?repo=vuejs/vue... | 2020-12-28T22:48:57 | 2020-12-28T22:48:57 | {} | MEMBER |
vuejs | core | 751,936,379 | 2,891 | edison1105 | > Can you add a test?
> It's also worth adding support for BigInt in templates
> See [vuejs/vue/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+Bigint](https://github.com/vuejs/vue/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+Bigint)
test case done!
I will open a new PR for support `BigInt` in template. | 2020-12-29T03:46:34 | 2020-12-29T03:46:34 | {} | MEMBER |
vuejs | core | 751,947,363 | 2,889 | edison1105 | @tabjy I think you can submit your PR if it is ready. | 2020-12-29T05:03:06 | 2020-12-29T05:03:06 | {} | MEMBER |
vuejs | core | 748,796,800 | 2,856 | 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%) | | 2020-12-21T06:47:47 | 2020-12-21T06:47:47 | {} | NONE |
vuejs | core | 749,200,549 | 2,859 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/2715 | 2020-12-21T21:18:45 | 2020-12-21T21:18:45 | {} | MEMBER |
vuejs | core | 749,478,287 | 2,751 | LinusBorg | > I think there is no way to infer SetupContext type from the usage of emit.
Yeah, I think there's not much to improve here as far as Vue's own types are concerned.
If you want to limit your function to certain event types, you will have to explicitly type them. The same is true for props, for example.
This is... | 2020-12-22T10:48:07 | 2020-12-22T10:48:07 | {
"+1": 1
} | MEMBER |
vuejs | core | 749,479,839 | 2,474 | LinusBorg | Documentation as been amended with proper instructions, we can close this here. | 2020-12-22T10:52:25 | 2020-12-22T10:52:25 | {} | MEMBER |
vuejs | core | 750,763,428 | 2,831 | dependabot-preview[bot] | Superseded by #2876. | 2020-12-24T06:16:38 | 2020-12-24T06:16:38 | {} | CONTRIBUTOR |
vuejs | core | 750,763,809 | 2,875 | 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%) | | 2020-12-24T06:17:52 | 2020-12-24T06:17:52 | {} | NONE |
vuejs | core | 751,237,055 | 2,882 | underfin | Oh.Sorry for mistaken. | 2020-12-25T11:38:47 | 2020-12-25T11:38:47 | {} | MEMBER |
vuejs | core | 748,506,073 | 2,841 | lee-orr | Thanks for the quick catch/solve! Hopefully it gets into the next release. | 2020-12-19T18:06:20 | 2020-12-19T18:06:20 | {
"heart": 1
} | NONE |
vuejs | core | 749,912,678 | 2,866 | Alanscut | @shlroland Maybe this is a bug of codesandbox, if you create an project with vue-cli, then it will trigger the handler. I have met this issue ever before. | 2020-12-23T03:46:48 | 2020-12-23T03:46:48 | {} | CONTRIBUTOR |
vuejs | core | 751,395,494 | 2,888 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 40.51 KB (-0.03% 🔽) |
| runtime-dom.global.prod.js | 26.83 KB (-0.04% 🔽) |
| size-check.global.prod.js | 16.21 KB (-0.1% 🔽) | | 2020-12-26T20:58:04 | 2020-12-26T20:58:04 | {} | NONE |
vuejs | core | 748,572,165 | 2,852 | mazaiting | > @mazaiting - I've resolved this issue by setting the `NODE_ENV`.
>
> `NODE_ENV=production npx rollup -c` - For example removes this error.
I think setting` NODE_ENV` is not a good solution, because this problem still occurs during the development process. | 2020-12-20T07:06:20 | 2020-12-20T07:06:20 | {} | NONE |
vuejs | core | 748,723,057 | 2,852 | mazaiting | > Read and follow https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro
> The error might be a miss configuration on a template. In that case open the issue on the template repo
> I think the question template I asked is compliant. Please point out where is the problem? | 2020-12-21T02:32:50 | 2020-12-21T02:32:50 | {} | NONE |
vuejs | core | 748,903,009 | 2,650 | LinusBorg | @posva We can just copy the file to each package's root once. the tarball contains more than the /dist folder. This way, we don't have to adjust anything about the build system. | 2020-12-21T10:37:41 | 2020-12-21T10:37:41 | {} | MEMBER |
vuejs | core | 748,959,617 | 2,837 | LinusBorg | I'll close this in favor of #2849 where we should work to find a more general solution to deal with readonly DOM props. | 2020-12-21T12:55:44 | 2020-12-21T12:55:44 | {} | MEMBER |
vuejs | core | 748,986,053 | 2,849 | posva | We could still cache it for perf reasons but I wonder if there isn't an exception in a particular browser that makes the property readonly without setting the proper flag (you never know with JS!)
I don't find having a list of exception that bad unless it begins to get too big. It also allows for specific checks and... | 2020-12-21T13:56:11 | 2020-12-21T13:56:40 | {} | MEMBER |
vuejs | core | 749,049,911 | 2,775 | LinusBorg | 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
| 2020-12-21T16:03:47 | 2020-12-21T16:03:47 | {
"+1": 12,
"rocket": 1
} | MEMBER |
vuejs | core | 749,919,650 | 2,866 | Alanscut | Could you try my project: https://github.com/Alanscut/vue-next-emit
and even I introduced it with cnd package, it still work well: https://github.com/Alanscut/vue-next-emit/blob/master/html/index.html
in the console, your will see '### handler has been triggered.' | 2020-12-23T04:10:47 | 2020-12-23T04:10:47 | {} | CONTRIBUTOR |
vuejs | core | 749,988,851 | 2,668 | Alanscut | Hi @Zcating , that's strange, I get the right result in your Reproduction link:
And even I create a project with vue-cli, the type of date is still `Date`.
```
Environment Info:
System:
OS:... | 2020-12-23T07:39:20 | 2020-12-23T09:07:39 | {} | CONTRIBUTOR |
vuejs | core | 751,223,877 | 2,882 | lgz5689 | >
>
> @underfin why this array default cannot set [] , only set [0],[{}] and more ?
> because this array render `el-option` ?
to be exact , this array default set [] , overwrite will be error , but default set [0],[{}] will not error | 2020-12-25T09:56:45 | 2020-12-25T09:56:45 | {} | NONE |
vuejs | core | 751,224,513 | 2,882 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/2820
When opening bug reports make sure to follow https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro | 2020-12-25T10:01:04 | 2020-12-25T10:01:04 | {} | MEMBER |
vuejs | core | 751,457,124 | 2,889 | tabjy | Hey @edison1105! Thanks for the timely reply. So is it confirmed to be a bug of Vue 3?
I am not sure if writing `serverPrefech` processing logic where you pointed is a good idea. To my limited knowledge of Vue:
1. `servePrefetch` is only related to SSR, namely the `server-renderer` package. Being a not standard l... | 2020-12-27T11:38:46 | 2020-12-27T13:22:32 | {} | NONE |
vuejs | core | 627,840,801 | 1,178 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/5102?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Dependabot will still automatically merge this pull request if you amend it and your test... | 2020-05-13T08:42:13 | 2020-05-13T08:42:13 | {} | CONTRIBUTOR |
vuejs | core | 629,121,153 | 1,174 | danyadev | In vue 2.x, I globally registered recursive components, but on version 3.x I do not know how to do this | 2020-05-15T09:01:24 | 2020-05-15T09:01:24 | {} | CONTRIBUTOR |
vuejs | core | 633,031,860 | 1,224 | underfin | Well.We can achieve it with use hmr api.I'm trying do it. | 2020-05-23T11:29:57 | 2020-05-23T11:29:57 | {} | MEMBER |
vuejs | core | 627,038,551 | 1,166 | Jinjiang | Gotcha. My quick idea is introducing another `refs="x"` for `v-for` which equals to `:ref="el => $refs.x[i] = el`. So it’s easy to code-mod and deprecate further I guess. Maybe will propose something like that later to RFCs. Thanks. | 2020-05-12T00:33:48 | 2020-05-12T00:33:48 | {} | MEMBER |
vuejs | core | 627,857,058 | 1,173 | sionzee | I haven't tried the externals way. I will try it and let you know.
Anyway shouldn't then the Vue be singleton library? I can imagine this can happen to many people.
There are just warnings\errors not related to this. So maybe checking global context if Vue is already loaded and add there message about this possible... | 2020-05-13T09:11:43 | 2020-05-13T09:11:43 | {
"+1": 2
} | NONE |
vuejs | core | 627,867,009 | 1,173 | pikax | > If I skip the vuex error. The vue warnings about transition are still there.
Can you update your repo with that code? | 2020-05-13T09:29:15 | 2020-05-13T09:29:15 | {} | MEMBER |
vuejs | core | 628,389,561 | 1,180 | hecateball | @underfin added my git repo to **Reproduction Link**. Please use this project. | 2020-05-14T05:08:38 | 2020-05-14T05:08:38 | {} | NONE |
vuejs | core | 628,626,868 | 1,181 | yyx990803 | @zeng450026937 fallthrough **should** cause the child to update, because it may get applied to the child root regardless of what the child's own render function uses. | 2020-05-14T13:14:49 | 2020-05-14T13:14:49 | {} | MEMBER |
vuejs | core | 628,674,258 | 1,181 | yyx990803 | 1. Fallthrough attributes are static most of the time.
2. Fallthrough attributes need to be properly merged with the component's own bindings, e.g. there is a `class` binding falling through AND the component itself also has a `class` binding. When a parent is updating a child, it's possible that the child's own sta... | 2020-05-14T14:30:43 | 2020-05-14T14:30:43 | {} | MEMBER |
vuejs | core | 629,635,153 | 1,194 | underfin | Please track here.https://github.com/vuejs/vite/issues/161 | 2020-05-16T12:03:16 | 2020-05-16T12:03:24 | {} | MEMBER |
vuejs | core | 631,842,396 | 1,211 | zhangenming | ok
I'm just curious.
Why do I find this so much more readable | 2020-05-21T02:33:51 | 2020-05-21T02:33:51 | {} | CONTRIBUTOR |
vuejs | core | 632,914,252 | 1,225 | yyx990803 | There will be documentation, but someone will have to find time to work on it.
Please don't open issues like this. | 2020-05-22T21:24:48 | 2020-05-22T21:25:18 | {} | MEMBER |
vuejs | core | 628,969,490 | 1,181 | yyx990803 | > For example, if we are performing a tweening animation on child component, that would be unacceptable.
The basic assumption is that **if a parent passes a dynamic prop to a child, then the child is expected to update when that prop changes.** That's how parent-child updates work. Even a React PureComponent updates... | 2020-05-15T01:19:54 | 2020-05-15T01:19:54 | {} | MEMBER |
vuejs | core | 629,111,935 | 1,190 | zhuxindaba | 相关rfc[rfcs](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0009-global-api-change.md#configoptionmergestrategies-behavior-change) | 2020-05-15T08:43:26 | 2020-05-15T08:43:26 | {} | NONE |
vuejs | core | 629,131,170 | 1,174 | danyadev | Thanks! | 2020-05-15T09:23:36 | 2020-05-15T09:23:36 | {} | CONTRIBUTOR |
vuejs | core | 630,600,360 | 1,196 | Arman19941113 | > This is probably has to do with your tsconfig and default import. Either way, not a Vue core issue.
Thanks!!! It's my webpack loader config error. I didn't use babel-loader after ts-loader. | 2020-05-19T06:01:01 | 2020-05-19T06:01:01 | {} | CONTRIBUTOR |
vuejs | core | 631,020,421 | 1,209 | aztalbot | Is it because `watch` doesn't run until the component mounts? I tried with `watchEffect` in your repro and I see "Updates: 1". | 2020-05-19T19:02:34 | 2020-05-19T19:02:34 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 631,029,116 | 1,205 | ambyjkl | Oh perfect, looks like i could've spent some time looking at open PRs, sorry :sweat_smile: | 2020-05-19T19:18:35 | 2020-05-19T19:18:35 | {} | NONE |
vuejs | core | 631,845,803 | 1,211 | Justineo | @zhangenming
F.Y.I. https://www.itamarweiss.com/personal/2018/02/28/return-early-pattern.html | 2020-05-21T02:45:41 | 2020-05-21T02:45:41 | {} | MEMBER |
vuejs | core | 627,277,979 | 1,172 | sionzee | In my opinion the proper way is to create computed array where is this value already fetched.
eg.: (renamed your users to userIds)
```
const users = computed(() => userIds.map(uId => getUser(uId)))
```
Everything what you call a variable can be converted to "computed" style. So why make it more complex? | 2020-05-12T11:17:43 | 2020-05-12T11:18:23 | {} | NONE |
vuejs | core | 627,861,732 | 1,173 | sionzee | I have put the globals into html head.
```html
<script type="text/javascript" src="https://unpkg.com/vue@3.0.0-beta.12/dist/vue.global.js"></script>
<script type="text/javascript" src="https://unpkg.com/vuex@4.0.0-beta.2/dist/vuex.global.js"></script>
```
- Added externals to webpack. (+ vuex) // copied your exa... | 2020-05-13T09:20:06 | 2020-05-13T09:29:03 | {} | NONE |
vuejs | core | 629,022,741 | 1,187 | zhuxindaba | > Could you please spent some time to read the [Document](https://vuejs.org/v2/guide/mixins.html) first?
I read the document again, but vue3 is actually different from vue2. Is a breaking change? | 2020-05-15T04:44:49 | 2020-05-15T04:44:49 | {} | NONE |
vuejs | core | 629,158,881 | 1,191 | LinusBorg | Refs can also be functions, which is what you would do here:
```javascript
const Tab = {
render(){
return Vue.h("div", {
ref: el => this.rootRef = el
}, this.divText);
},
// ... rest of your code...
```
To correctly end up with an empty ref if the element disappears, ie.e. because o... | 2020-05-15T10:26:09 | 2020-05-15T10:27:54 | {
"hooray": 1
} | MEMBER |
vuejs | core | 630,845,577 | 1,206 | lzhoucs | @LinusBorg thanks for the comment. If you take a look at https://github.com/vuejs/vue-next/issues/1186, I moved it out of the children function as a workaround. That's why I said
> The code is in the demo is from the last state of #1186
My question then becomes is there a way to get both #1186 and this ticket t... | 2020-05-19T14:11:43 | 2020-05-19T14:11:43 | {} | NONE |
vuejs | core | 632,567,157 | 1,222 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: check-size](https://circleci.com/gh/vuejs/vue-next/5328?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Dependabot will still automatically merge this pull request if you amend it and you... | 2020-05-22T08:25:24 | 2020-05-22T08:25:24 | {} | CONTRIBUTOR |
vuejs | core | 626,849,927 | 1,164 | sqal | Optional props decalration has been removed in [alpha.11](https://github.com/vuejs/vue-next/blob/master/CHANGELOG.md#300-alpha11-2020-04-04) (check RFC for more details). Either declare buttonText as prop or access it from `context.attrs`
Also `on: { click: () => {} }` is not a valid code. Vue 3 moved to flat data s... | 2020-05-11T17:42:08 | 2020-05-11T17:42:08 | {} | CONTRIBUTOR |
vuejs | core | 626,857,730 | 1,165 | yyx990803 | This is expected behavior. `v-if` has higher priority than `v-for` so it doesn't have access to `v-for` scope: [compiler output]( https://vue-next-template-explorer.netlify.app/#%7B%22src%22%3A%22%3Cdiv%20v-for%3D%5C%22a%20in%20%5B1%2C%202%2C%203%5D%5C%22%20v-if%3D%5C%22a%20%3E%201%5C%22%3E%5Cn%20%20%20%20%7B%7B%20a%20... | 2020-05-11T17:55:38 | 2020-05-11T17:56:29 | {} | MEMBER |
vuejs | core | 627,052,052 | 1,164 | Amour1688 | > Optional props decalration has been removed in [alpha.11](https://github.com/vuejs/vue-next/blob/master/CHANGELOG.md#300-alpha11-2020-04-04) (check RFC for more details). Either declare buttonText as prop or access it from `context.attrs`
>
> Also `on: { click: () => {} }` is not a valid code. Vue 3 moved to flat ... | 2020-05-12T01:21:48 | 2020-05-12T01:21:48 | {} | MEMBER |
vuejs | core | 627,989,378 | 1,173 | yyx990803 | Why are you using window to communicate across chunks when you are using multi-entry build with webpack? Just import as normal and webpack should code split accordingly.
Either way, this is not a vue-next problem. | 2020-05-13T13:33:12 | 2020-05-13T13:33:12 | {} | MEMBER |
vuejs | core | 629,007,511 | 1,187 | Kagashino | Could you please spent some time to read the [Document](https://vuejs.org/v2/guide/mixins.html) first? | 2020-05-15T03:37:29 | 2020-05-15T03:37:29 | {} | NONE |
vuejs | core | 631,318,348 | 1,216 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/5301?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Dependabot will still automatically merge this pull request if you amend it and your test... | 2020-05-20T08:19:24 | 2020-05-20T08:19:24 | {} | CONTRIBUTOR |
vuejs | core | 631,843,249 | 1,211 | yyx990803 | It's subjective. And it's best not to submit PRs for subjective/preference related changes. | 2020-05-21T02:36:52 | 2020-05-21T02:36:52 | {} | MEMBER |
vuejs | core | 628,986,796 | 1,185 | 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... | 2020-05-15T02:19:52 | 2020-05-15T02:19:52 | {} | CONTRIBUTOR |
vuejs | core | 629,112,273 | 1,187 | zhuxindaba | > Well, I found the relative [rfcs](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0009-global-api-change.md#configoptionmergestrategies-behavior-change), it may help you.
>
> There is no more `defaultStrat` in 3.0. Users must now always provide their own merge strategy functions instead of reusing built-in s... | 2020-05-15T08:44:12 | 2020-05-15T08:44:12 | {} | NONE |
vuejs | core | 629,262,346 | 1,186 | lzhoucs | Thanks @underfin . I intentionally have two variables: `active` is for the new value, `wasActive` is for the current value before being updated by the new value. setting `active` works, however getting `wasActive` doesn't. Your following comment makes sense:
```
const wasActive = vnode.props.active// it is origin vno... | 2020-05-15T14:20:18 | 2020-05-15T14:20:18 | {} | NONE |
vuejs | core | 631,294,042 | 1,211 | zhangenming | Just changed the way the entry is judged on the first line | 2020-05-20T07:34:29 | 2020-05-20T07:34:29 | {} | CONTRIBUTOR |
vuejs | core | 632,664,098 | 1,221 | yyx990803 | When pre compiling templates, it needs to be configured at the compiler level. | 2020-05-22T12:21:19 | 2020-05-22T12:21:19 | {} | MEMBER |
vuejs | core | 626,968,071 | 1,167 | yyx990803 | It's lowercase `<component>` only. Uppercase is considered a custom component. | 2020-05-11T21:14:16 | 2020-05-11T21:14:16 | {
"+1": 2
} | MEMBER |
vuejs | core | 627,237,018 | 1,164 | sqal | @Amour1688
No, you don't have to. All attributes (also listeners) that are not declared as prop will be placed in `context.attrs`, so if you have to pass it to some node in the render function use that object, here'a an example:
```js
function SuperButton(props, context) {
return h('div', [
'Super',
... | 2020-05-12T09:52:37 | 2020-05-12T09:52:37 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 627,824,560 | 1,173 | pikax | The issue is cause by the build.
If you check your `dist` files yill find they are **huge** (~900kb each and 76kb prod).
This is cause each compiled file containing the vue3 code. Altho in you code you only access the the vue through `window.Vue`, and that should cause a problem, but because you are compiling the... | 2020-05-13T08:11:54 | 2020-05-13T08:11:54 | {} | MEMBER |
vuejs | core | 627,853,405 | 1,173 | pikax | > It will still keep throwing the errors. (I have checked it and there is only 1 Vue library)
The issue is the `vue-loader` result, as shown in my previous comment
```ts
// compiled template
import { /* imports */ } from "vue" // this is the other `vue` instance that's messing with the rest
```
EDIT: Have you... | 2020-05-13T09:05:15 | 2020-05-13T09:07:42 | {} | MEMBER |
vuejs | core | 628,645,343 | 1,181 | zeng450026937 | If child component render a large list, which should be a noticeable impact. | 2020-05-14T13:43:40 | 2020-05-14T13:43:40 | {} | NONE |
vuejs | core | 629,485,629 | 1,178 | dependabot-preview[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`.
If you change your mind, just re-... | 2020-05-15T21:08:36 | 2020-05-15T21:08:36 | {} | CONTRIBUTOR |
vuejs | core | 629,584,148 | 1,186 | lzhoucs | Thanks @underfin . I realized that as well after I replied. I made a change and it now works. Not sure if it is good practice or not, but it works: https://codepen.io/lzhoucs/pen/jObeqvb
Close the ticket since there's no bug to fix but a mistake on my side. | 2020-05-16T04:00:59 | 2020-05-16T04:00:59 | {} | NONE |
vuejs | core | 629,894,804 | 1,187 | zhuxindaba | not a bug | 2020-05-18T01:14:53 | 2020-05-18T01:14:53 | {} | NONE |
vuejs | core | 630,234,469 | 1,175 | underfin | > Does #1151 contain tests for this?
No.The #1151 test is written with master code.I add `fixme` comment.
You can look at #1151 first.If that no problem, I will update and change test with this pr. | 2020-05-18T14:50:54 | 2020-05-18T14:50:54 | {} | MEMBER |
vuejs | core | 628,337,186 | 1,180 | underfin | Can you provider an whole project with this? | 2020-05-14T01:48:33 | 2020-05-14T01:48:33 | {} | MEMBER |
vuejs | core | 629,056,702 | 1,189 | underfin | Should reslove option data order: mixin data => comp data => check data duplicate.
The order of reslove watch is same as data. | 2020-05-15T06:34:34 | 2020-05-15T06:34:34 | {} | MEMBER |
vuejs | core | 630,060,878 | 1,195 | pikax | Can you provide how to reproduce the error that you were seeing?
Can you add a test on the `test-dts` folder? | 2020-05-18T09:26:53 | 2020-05-18T09:26:53 | {
"+1": 1
} | MEMBER |
vuejs | core | 630,256,212 | 1,197 | CyberAP | > Great work! I think the implementation looks good.
>
> Obviously we should try to reduce the redundancy by reusing some of the duplicated logic - I can do that but it will have to wait until I finish other priorities. Would you be interested in working on that in the meanwhile?
Sure, I'll mention you when it's ... | 2020-05-18T15:24:02 | 2020-05-18T15:24:02 | {} | CONTRIBUTOR |
vuejs | core | 631,980,926 | 1,220 | Justineo | This is not a valid feature request, thanks. | 2020-05-21T09:19:31 | 2020-05-21T09:19:31 | {} | MEMBER |
vuejs | core | 631,990,804 | 1,220 | zhangenming | > This is not a valid feature request, thanks.
sorry
So what does this thing belong to and how should it be pushed forward | 2020-05-21T09:41:37 | 2020-05-21T09:41:37 | {} | CONTRIBUTOR |
vuejs | core | 626,856,973 | 1,154 | yyx990803 | See 5b8883a8
`dynamicChildren` should always be non-null for block nodes since it's used to check if the vnode is actually a block. | 2020-05-11T17:54:16 | 2020-05-11T17:54:16 | {} | MEMBER |
vuejs | core | 626,859,532 | 1,166 | yyx990803 | Actually, we may need to detect non composition api usage for backwards compat. Or we need an RFC to officially deprecate this (I never considered it good practice anyway, and it creates a TON of complexity when used inside nested `v-for`s.) | 2020-05-11T17:58:42 | 2020-05-11T17:59:36 | {
"+1": 7
} | MEMBER |
vuejs | core | 627,822,398 | 1,174 | LinusBorg | ```
components: {
Bar: () => Promise.resolve(Bar)
},
```
This is not a valid component definition. async components need to be wrapped with `defineAsyncComponent()` in Vue 3.
```
components: {
Bar: defineAsyncComponent(() => Promise.resolve(Bar))
},
```
Updated, working Fiddle: https://jsfiddle.net... | 2020-05-13T08:07:36 | 2020-05-13T08:07:53 | {
"+1": 6,
"rocket": 2
} | MEMBER |
vuejs | core | 629,071,778 | 1,186 | underfin | ```js
const active = vnode.props.href === props.modelValue
const wasActive = vnode.props.active// it is origin vnode props. it hasn't active props.
console.log(vnode.props.href, wasActive)
console.log(vnode.props.href, active) // it will be expect to you.
return... | 2020-05-15T07:13:28 | 2020-05-15T07:14:38 | {} | MEMBER |
vuejs | core | 626,966,702 | 1,168 | yyx990803 | It's working as intended?... | 2020-05-11T21:11:44 | 2020-05-11T21:11:44 | {} | MEMBER |
vuejs | core | 626,972,634 | 1,168 | 5onderling | Happens to me in Chrome, but not Firefox.
`addEventListener('click', console.log);` logs after I select an option with my mouse.
 | 2020-05-11T21:23:12 | 2020-05-11T21:35:13 | {} | NONE |
vuejs | core | 627,749,499 | 1,114 | zuozuomuxi | It's strange that stateful components and functional components declare props in different ways, Hope to have a better way like #1155. | 2020-05-13T05:10:18 | 2020-05-13T05:10:18 | {} | NONE |
vuejs | core | 628,640,802 | 1,181 | zeng450026937 | @yyx990803 Because fallthrough attrs is considered has no effect to child component, why not just use the previous vnode tree and patch it with new fallthrough attrs, but calling child render function to get a completely same vnode tree? | 2020-05-14T13:37:37 | 2020-05-14T13:37:37 | {} | NONE |
vuejs | core | 629,574,683 | 1,186 | underfin | ```
const children = slots.default ? slots.default() : []
```
For every update will create new children, and each of the new child never has active props. | 2020-05-16T02:20:28 | 2020-05-16T02:20:28 | {
"+1": 1
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.