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 | docs | 791,520,059 | 928 | guusvandewal | > Thanks for the PR.
>
> Based on line 51, I think the intention is that you would call it as:
>
> ```
> {{ $translate('greetings.hello') }}
> ```
>
> As far as I can tell this is working correctly.
Yes, that is correct. Bit silly of me. I closed the PR | 2021-03-05T16:13:26 | 2021-03-05T16:14:36 | {} | NONE |
vuejs | docs | 774,636,795 | 845 | LinusBorg | https://v3.vuejs.org/guide/migration/events-api.html#overview
If you need help, ask in chat.vuejs.org | 2021-02-07T08:49:31 | 2021-02-07T08:50:11 | {} | MEMBER |
vuejs | docs | 782,933,470 | 867 | kospl | @skirtles-code yeah, seems Google went all wrong with handling web storage in incognito mode https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API#private_browsing_incognito_modes
btw works in Edge when in incognito mode. | 2021-02-21T21:51:39 | 2021-02-21T21:51:39 | {} | NONE |
vuejs | docs | 794,006,950 | 908 | NataliaTepluhina | First of all, we have it mentioned here with function syntax: https://v3.vuejs.org/api/instance-methods.html#watch
'll create a PR to add watching a single nested property to API reference for now. | 2021-03-09T14:56:57 | 2021-03-09T15:30:08 | {} | MEMBER |
vuejs | docs | 794,157,756 | 927 | ITenthusiasm | Got it. Thanks! | 2021-03-09T16:55:01 | 2021-03-09T16:55:01 | {} | NONE |
vuejs | docs | 794,566,487 | 932 | skirtles-code | I understand why this would be desirable but I'm not sure whether it would be practical. New pages are added to the documentation all the time and there is inevitably a delay before those pages are added to the translations. | 2021-03-09T22:52:14 | 2021-03-09T22:52:14 | {} | CONTRIBUTOR |
vuejs | docs | 802,215,406 | 937 | NataliaTepluhina | @skirtles-code @danielroe would you mind checking this draft? It's very raw so far, any suggestions/improvements are much appreciated! 🙇🏻♀️ | 2021-03-18T19:08:56 | 2021-03-18T19:08:56 | {
"+1": 1
} | MEMBER |
vuejs | docs | 803,653,857 | 956 | joaomelo | I aimed to find some a synonym in order to be consistent with the original page content since the whole documentation is so well written.
I also found "passlist" and "safelist" as alternatives. If you think one of these options is more appropriate, I can make the change. If the issue persists, I sure can try to reph... | 2021-03-21T20:23:39 | 2021-03-21T20:23:39 | {} | CONTRIBUTOR |
vuejs | docs | 721,656,606 | 666 | u-sho | @phanan I see.
I appreciate for your review :bow: | 2020-11-04T10:44:25 | 2020-11-04T10:44:25 | {} | CONTRIBUTOR |
vuejs | docs | 723,476,646 | 677 | skirtles-code | You raise a really good point.
As far as I can tell, this is the first time the Composition API is mentioned anywhere in the guide. The paragraph just before this example uses various terms that the reader won't have met yet. There's no acknowledgement (in that paragraph) that these are concepts from later in the gu... | 2020-11-07T18:10:59 | 2020-11-07T18:10:59 | {} | CONTRIBUTOR |
vuejs | docs | 727,565,467 | 683 | nmezzopera | > This is a good start 🤩
>
> Maybe we can add notes about typescript and vetur support too.
@znck Thanks! I've applied all the suggestions 😄 about Typescript, it falls out of my experience (I know I have to catch up with Typescript 😅 ) And I've never configured Vetur for vue3.
Do you think this is super i... | 2020-11-15T12:54:38 | 2020-11-15T12:54:38 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 727,595,464 | 692 | LinusBorg | To be sure, is your issue here that people might forget to
1. not use `reacive()` on such objects in the first place and
2. use `markRaw()` on such an instance when adding it as property value on a reactive object?
A small code example of the pitfalls you wanna see improved would help. | 2020-11-15T16:17:41 | 2020-11-15T16:18:31 | {} | MEMBER |
vuejs | docs | 730,821,937 | 702 | skirtles-code | There are some tweaks needed in the docs and I've got a first draft of those locally. However, there's something more going on here.
Most of the documentation examples do not show a warning when run in isolation, even though they don't include `emits`. The warning isn't supposed to be shown when `emits` isn't specif... | 2020-11-20T03:28:19 | 2020-11-20T03:28:19 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | docs | 733,446,713 | 710 | skirtles-code | There is some discussion of this on the previous page of the documentation:
https://v3.vuejs.org/guide/instance.html#component-instance-properties
All of the properties of `this` (also referred to as `vm`) are available in the template. The section I referenced lists the component options that are typically used ... | 2020-11-25T03:54:00 | 2020-11-25T03:54:00 | {} | CONTRIBUTOR |
vuejs | docs | 734,419,470 | 437 | iazz | I'm really glad that key paths are now supported in watch options, but that should probably be explicitly mentioned in the docs, as the docs for $watch do mention that they are not, hence the ambiguity. | 2020-11-26T17:35:57 | 2020-11-26T17:35:57 | {
"+1": 1
} | NONE |
vuejs | docs | 739,312,792 | 730 | NataliaTepluhina | @JensD98 thank you so much for this addition! The only fix here: could we reuse the example from above instead of changing it to use a different prop so readers would have a smooth transition? | 2020-12-05T15:48:01 | 2020-12-05T15:48:01 | {} | MEMBER |
vuejs | docs | 745,900,232 | 748 | skirtles-code | This issues list is for reporting problems with the documentation.
For usage questions, please use the [Vue Discord chat](https://chat.vuejs.org/), the [Vue Forum](https://forum.vuejs.org/) or [Stack Overflow](https://stackoverflow.com/). | 2020-12-16T08:23:37 | 2020-12-16T08:23:37 | {} | CONTRIBUTOR |
vuejs | docs | 730,772,494 | 702 | skirtles-code | I'll put in a PR for this. It looks like a few of the `v-model` examples need updating. | 2020-11-20T01:21:42 | 2020-11-20T01:21:42 | {} | CONTRIBUTOR |
vuejs | docs | 736,714,109 | 721 | IlCallo | Related to `ComponentCustomOptions` augmentation, which is they way to specify the context (both of Options API and what has been returned by the setup method) to a method added as option?
Previously we're using this syntax on Quasar Framework
```ts
declare module 'vue/types/options' {
interface ComponentOption... | 2020-12-01T17:47:56 | 2020-12-01T17:47:56 | {} | NONE |
vuejs | docs | 737,071,236 | 30 | posva | I can take this one, I did it for Vue Router docs | 2020-12-02T08:20:49 | 2020-12-02T08:20:49 | {} | MEMBER |
vuejs | docs | 744,383,560 | 505 | EmielSchmeink | Is there an ETA on when this migration guide will be live? | 2020-12-14T11:40:02 | 2020-12-14T11:40:02 | {} | NONE |
vuejs | docs | 729,877,865 | 700 | skirtles-code | At the RFC stage it was documented here:
https://github.com/vuejs/rfcs/blob/master/active-rfcs/0009-global-api-change.md
It seems that it didn't make it through to the equivalent page in the migration guide, perhaps because it was a late addition to the RFC.
It definitely needs to be in the migration guide som... | 2020-11-18T18:40:55 | 2020-11-18T18:40:55 | {} | CONTRIBUTOR |
vuejs | docs | 739,313,166 | 728 | NataliaTepluhina | @robinzimmermann thank you for catching this! I've updated the codepen 👍🏻 | 2020-12-05T15:51:18 | 2020-12-05T15:51:18 | {} | MEMBER |
vuejs | docs | 720,356,696 | 660 | nmezzopera | @NataliaTepluhina Thanks for showing me this! As I've just recently went through this exact process for: https://github.com/vue-leaflet/vue-leaflet
I can summarise my experience on an addition for the docs (since is rather fresh!) I would touch this points:
- General intro
- How to use the composition API (in a ... | 2020-11-02T09:38:51 | 2020-11-02T09:39:14 | {} | CONTRIBUTOR |
vuejs | docs | 720,460,306 | 660 | znck | @DonNicoJs feel free to reach me, regarding RPV or anything else needed for this. | 2020-11-02T13:06:18 | 2020-11-02T13:06:18 | {} | MEMBER |
vuejs | docs | 720,566,103 | 668 | skirtles-code | I think we should hold off on merging this until it is confirmed that this is an intended change. Using a `key` may be necessary with 3.0.2 but https://github.com/vuejs/vue-next/issues/2535 is currently marked as an open bug. I dare say there'll be more discussion on that issue over the next few days. | 2020-11-02T16:07:24 | 2020-11-02T16:07:24 | {
"+1": 4
} | CONTRIBUTOR |
vuejs | docs | 724,436,071 | 685 | beiding110 | @skirtles-code Oh, oh, I find it. You're right. Your fix is more accurate.
| 2020-11-10T04:05:16 | 2020-11-10T04:05:16 | {} | CONTRIBUTOR |
vuejs | docs | 730,826,994 | 702 | floydback | > Do you have any global mixins in your application, consistent with my theory?
Yes! I can confirm this. Right now I've remove a plugin (it add global mixin) and this warning go away.
I also tried to reproduce this warning but it didn't show up on a pure project. I could not understand what is the reason. I think... | 2020-11-20T03:47:49 | 2020-11-20T03:47:49 | {} | NONE |
vuejs | docs | 731,523,283 | 703 | Derek-DZ | @NataliaTepluhina in version 3.0.2 get the wrong result too. | 2020-11-21T07:36:00 | 2020-11-21T07:36:00 | {} | NONE |
vuejs | docs | 737,679,407 | 725 | NataliaTepluhina | Hi @softboy99! Options API is not 'old' or 'Vue 2' API, it still remains as valid as the Composition API and we decided to leave it as the main learning path for people just picking up Vue. Composition API is designed to solve the problem of code abstraction and reusability mostly, so we start with it a bit later.
S... | 2020-12-03T05:41:20 | 2020-12-03T05:41:20 | {} | MEMBER |
vuejs | docs | 739,481,771 | 732 | cRAN-cg | Aah my bad, the markdown compiler used by Github is different than what is used on the docs site. Everything works perfect. While browsing though the Github repo though it looked odd. Closing this.
[For my future reference](https://vuepress.vuejs.org/guide/markdown.html#line-highlighting-in-code-blocks) | 2020-12-06T10:14:12 | 2020-12-06T10:28:03 | {} | NONE |
vuejs | docs | 729,650,579 | 693 | skirtles-code | I wasn't expecting the URLs to change. Can it be moved to a separate sidebar without changing the URLs? | 2020-11-18T12:38:11 | 2020-11-18T12:38:11 | {} | CONTRIBUTOR |
vuejs | docs | 729,727,734 | 693 | NataliaTepluhina | @skirtles-code I've checked and it's actually possible, we just need to define a `guide/migration` in the sidebar settings before `guide` | 2020-11-18T14:47:55 | 2020-11-18T14:47:55 | {
"+1": 1
} | MEMBER |
vuejs | docs | 733,694,538 | 711 | skirtles-code | I think there may be even more nuance lurking beneath the surface here.
From what I can tell:
* Normal (non-boolean) attributes will be omitted if their value is `undefined` or `null`. All other values are converted to strings.
* For boolean attributes the values `undefined`, `null`, `false`, `0` and `NaN` will ... | 2020-11-25T13:05:01 | 2020-11-25T13:05:01 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 735,368,023 | 683 | NataliaTepluhina | @DonNicoJs @skirtles-code thank you both so much for authoring the addition and for the thorough review! I believe right now there are no major blockers for merging this one and we can handle additions like TS in the follow-ups | 2020-11-29T09:48:03 | 2020-11-29T09:48:03 | {} | MEMBER |
vuejs | docs | 722,680,109 | 598 | gtsiolis | Can't reproduce this. 😭 | 2020-11-05T22:22:27 | 2020-11-05T22:22:27 | {} | NONE |
vuejs | docs | 735,988,479 | 420 | scaredyfish | The lack of Vue.set really confused me for some time. It should at least be documented under https://v3.vuejs.org/guide/migration/introduction.html#removed-apis | 2020-11-30T19:20:04 | 2020-11-30T19:20:04 | {} | NONE |
vuejs | docs | 736,636,528 | 656 | NataliaTepluhina | We've discussed this at the core team meeting and the plan is to change the recommended casing to the way we have for props:
- on the child component, we emit the event and declare it in the `emits` option in the camelCase;
- on the parent component, we listen to events in kebab-case (so in-DOM templates work fine)... | 2020-12-01T15:45:05 | 2020-12-01T15:45:18 | {} | MEMBER |
vuejs | docs | 737,218,236 | 722 | skirtles-code | I tried this myself and I see the same change:
* Vue 2: https://jsfiddle.net/skirtle/5mhLtuqx/
* Vue 3: https://jsfiddle.net/skirtle/fo1bh34x/
@LongTengDao Do you have any confirmation that this is an intentional change and not just a bug? | 2020-12-02T13:05:27 | 2020-12-02T13:05:27 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 737,685,251 | 725 | softboy99 | Hi，
Thanks, ok, if so, could you please make notes on the doc that this is code options api or composition api?some code are combined together these two. | 2020-12-03T05:58:50 | 2020-12-03T05:58:50 | {} | NONE |
vuejs | docs | 739,314,066 | 724 | NataliaTepluhina | @posva looks really nice! Should we remove the `Draft` state and merge the PR? | 2020-12-05T15:58:50 | 2020-12-05T15:58:50 | {} | MEMBER |
vuejs | docs | 739,315,785 | 724 | posva | Is the background solution satisfactory enough?
I'm only worried because I'm using hacky stuff in CSS but I couldn't figure out a different way 😓 | 2020-12-05T16:13:24 | 2020-12-05T16:13:24 | {} | MEMBER |
vuejs | docs | 722,976,154 | 676 | LinusBorg | You seem to be looking at an out-of date version of the source, what version did you check?
https://github.com/vuejs/vue-next/blob/43579a8de358846de96d0d789eebbebf95b2f391/packages/runtime-core/src/apiWatch.ts#L266-L269 | 2020-11-06T09:28:50 | 2020-11-06T09:28:50 | {
"+1": 1
} | MEMBER |
vuejs | docs | 722,977,417 | 676 | wocaatm | > You seem to be looking at an out-of date version of the source, what version did you check?
>
> https://github.com/vuejs/vue-next/blob/43579a8de358846de96d0d789eebbebf95b2f391/packages/runtime-core/src/apiWatch.ts#L266-L269
ok，the souce code is out-of date, thx | 2020-11-06T09:31:26 | 2020-11-06T09:31:26 | {} | NONE |
vuejs | docs | 724,676,414 | 687 | ArkIv |
It is very convenient to work with one object without copying it to add property changes,
And even in combination with provide ().
Generally after
**default: () => {
return reactive ([{xxxx}, {yyy}, {. . .}])**
The object, as it were, ceases to be Default, it is used only in this component and only in th... | 2020-11-10T12:39:44 | 2020-11-10T12:39:44 | {} | NONE |
vuejs | docs | 725,247,934 | 687 | skirtles-code | This isn't specific to the `default`. In general the values of `props` are not made reactive. They'll only be reactive if the value passed by the parent was already reactive.
The same is true of objects returned by `computed` properties. The property itself is reactive but the value is not. Again, if the object retu... | 2020-11-11T07:06:50 | 2020-11-11T07:06:50 | {} | CONTRIBUTOR |
vuejs | docs | 736,823,014 | 656 | ota-meshi | Thank you for discussing this issue! I think it makes sense. | 2020-12-01T21:11:38 | 2020-12-01T21:11:38 | {} | MEMBER |
vuejs | docs | 742,643,535 | 742 | smasinde | Decided to use a per route route guard option. | 2020-12-10T16:46:06 | 2020-12-10T16:46:06 | {} | NONE |
vuejs | docs | 724,933,554 | 598 | thedamon | I tried it again.. looks like the issue happens if I am scrolled down on the page. | 2020-11-10T19:59:56 | 2020-11-10T19:59:56 | {} | CONTRIBUTOR |
vuejs | docs | 727,834,422 | 692 | jods4 | To add a little bit of context: how did I stumble upon this?
Like everyone else I'm sure, I didn't give this a thought beforehand.
My dates got proxified inside some reactive graph, I wasn't aware.
I noticed it because it created some changes in behavior, which turned into bugs. | 2020-11-16T08:53:48 | 2020-11-16T08:53:48 | {} | NONE |
vuejs | docs | 731,587,316 | 683 | nmezzopera | @@skirtles-code Thank you so much for the review! And apologies for the slow turn-around, I manage to scavenge time for OSS only during the weekend 🙇 I think I've addressed all the points! | 2020-11-21T14:31:22 | 2020-11-21T14:31:22 | {} | CONTRIBUTOR |
vuejs | docs | 731,634,873 | 656 | skirtles-code | There's a related bug for using kebab-case with `emits`: https://github.com/vuejs/vue-next/issues/2540
I haven't seen anything official but it would seem that the intention is for event names to treat kebab-case and camelCase as equivalent in Vue 3, a bit like props. Assuming that is the case, it would make sense to... | 2020-11-21T20:50:31 | 2020-11-21T20:50:31 | {} | CONTRIBUTOR |
vuejs | docs | 734,811,124 | 716 | skirtles-code | This issues list is for reporting problems with the documentation.
For usage questions please use the [Vue Discord chat](https://chat.vuejs.org/), the [Vue Forum](https://forum.vuejs.org/) or [Stack Overflow](https://stackoverflow.com/). | 2020-11-27T12:25:03 | 2020-11-27T12:25:03 | {} | CONTRIBUTOR |
vuejs | docs | 735,353,511 | 718 | skirtles-code | Thank you for the PR but I don't think this change is correct.
The preceding code uses `v-bind:value="a"`, which binds the value of the `a` property to the radio. It doesn't bind the string `'a'`. | 2020-11-29T07:04:52 | 2020-11-29T07:04:52 | {} | CONTRIBUTOR |
vuejs | docs | 735,373,570 | 683 | nmezzopera | @NataliaTepluhina Thank you very much! 🙇 🙇 | 2020-11-29T10:44:09 | 2020-11-29T10:44:09 | {} | CONTRIBUTOR |
vuejs | docs | 736,653,053 | 694 | IlCallo | https://github.com/vuejs/docs-next/issues/694
Is this the same problem? Cause there are examples on how to do this into the TSDocs of the related interfaces | 2020-12-01T16:11:30 | 2020-12-01T16:11:30 | {} | NONE |
vuejs | docs | 743,078,946 | 711 | skirtles-code | I'm going to have a go at updating this unless I hear otherwise. | 2020-12-11T09:23:11 | 2020-12-11T09:23:11 | {} | CONTRIBUTOR |
vuejs | docs | 720,497,222 | 667 | phanan | Great catch, thanks! | 2020-11-02T14:14:41 | 2020-11-02T14:14:41 | {
"+1": 1
} | MEMBER |
vuejs | docs | 724,417,150 | 685 | skirtles-code | I agree there's a problem with that example but I don't think this is quite the right fix.
The equivalent example in the Vue 2 docs is here:
https://vuejs.org/v2/guide/components-slots.html#Abbreviated-Syntax-for-Lone-Default-Slots
I think the Vue 2 example is correct and something has been lost in the migrati... | 2020-11-10T02:56:42 | 2020-11-10T02:56:42 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 724,582,163 | 687 | NataliaTepluhina | Thank you for creating an issue!
I am not completely sure what is the case where you need a default value of the prop to be reactive. It's only used as a fallback in the case if you didn't pass any value from the parent component, and you're not supposed to mutate a prop (or its default value) from the child compone... | 2020-11-10T09:33:22 | 2020-11-10T09:33:22 | {} | MEMBER |
vuejs | docs | 727,914,858 | 693 | skirtles-code | I have also found it difficult to navigate within the Migration Guide because of its inclusion in the main Guide sidebar. I would be in favour of using a separate sidebar for the Migration Guide.
From a naming perspective, I wonder whether *'Migration from Vue 2'* in the menu would be more helpful. Someone with an e... | 2020-11-16T11:17:23 | 2020-11-16T11:17:23 | {} | CONTRIBUTOR |
vuejs | docs | 731,913,905 | 618 | calali | I'm sorry for late reply.
My mac's os is macOS Mojave and it's version is 10.14.6 (18G6032).
And the browser is Google Chrome, it's version is 87.0.4280.67(official version) (x86_64). | 2020-11-23T03:57:06 | 2020-11-23T03:57:58 | {} | NONE |
vuejs | docs | 739,318,678 | 730 | JensDll | @NataliaTepluhina I can see what you mean. However, I feel like having an object with three properties for demonstrating default values two times can get a bit lengthy. Would adding the numbers array prop to the example above already help? | 2020-12-05T16:39:38 | 2020-12-05T16:39:38 | {} | CONTRIBUTOR |
vuejs | docs | 727,832,486 | 692 | jods4 | To illustrate my response, let's consider `DateTime` from Luxon. Suppose I use this as a replacement for the built-in `Date`.
1. Is unavoidable, given the deep-by-default philosophy of Vue.
Let's create a reactive arrays of some dates:
```js
let holidays = reactive(['2020-12-25', '2020-12-31'].map(DateTime.fromIS... | 2020-11-16T08:50:15 | 2020-11-16T08:50:15 | {} | NONE |
vuejs | docs | 729,493,689 | 695 | NataliaTepluhina | I believe this issue should be opened on VueRouter repo as we don't cover router in the core documentation. | 2020-11-18T07:32:49 | 2020-11-18T07:32:49 | {} | MEMBER |
vuejs | docs | 736,699,747 | 721 | IlCallo | ```ts
declare module '@vue/runtime-core' {
interface ComponentCustomOptions {
beforeRouteUpdate?(
to: Route,
from: Route,
next: () => void
): void
}
}
```
AFAIK this way of declaring a new option (written as example into TSDocs) would actually overwrite `@vue/runtime... | 2020-12-01T17:24:13 | 2020-12-01T17:24:13 | {} | NONE |
vuejs | docs | 739,138,770 | 695 | caitoucom | 遇到了相同的问题，不知道您有没有解决呢 | 2020-12-05T07:22:27 | 2020-12-05T07:22:27 | {} | NONE |
vuejs | docs | 739,416,182 | 734 | fimion | @bencodezen told me to tag him in this as well. | 2020-12-05T21:07:15 | 2020-12-05T21:07:15 | {} | CONTRIBUTOR |
vuejs | docs | 739,466,217 | 724 | NataliaTepluhina | @posva I think it's justified to be hacky 😅 | 2020-12-06T07:18:15 | 2020-12-06T07:18:15 | {} | MEMBER |
vuejs | docs | 739,487,104 | 695 | shuyuhan01 | > 遇到了相同的问题，不知道您有没有解决呢
您好！有解决。我是在router 的文件里面的index.ts
import { createRouter, createWebHashHistory, RouteRecordRaw } from "vue-router"
const rouTer = createWebHashHistory(process.env.BASE_URL).state.current
store.dispatch('setrouTer',rouTer)
通过这样的形式 刷新浏览器就可以找到当前路由所要的信息 | 2020-12-06T11:06:21 | 2020-12-06T11:06:21 | {} | NONE |
vuejs | docs | 746,090,320 | 751 | EdisonVan | 1920*1080 , thanks | 2020-12-16T10:52:07 | 2020-12-16T10:52:07 | {} | NONE |
vuejs | docs | 731,204,712 | 703 | NataliaTepluhina | @Derek-DZ is this reproducing on the current version (3.0.2 as of today)? | 2020-11-20T14:32:55 | 2020-11-20T14:32:55 | {} | MEMBER |
vuejs | docs | 736,171,456 | 720 | leeboo | got it, thanks | 2020-12-01T02:15:50 | 2020-12-01T02:15:50 | {} | NONE |
vuejs | docs | 739,438,771 | 732 | skirtles-code | Could you provide some more details about why you think this change is necessary? The existing line, ` ```js{7-15} `, indicates that lines 7 to 15 should be highlighted with a different background colour and that does appear to be working. Are you suggesting that those lines shouldn't be highlighted? | 2020-12-06T01:04:37 | 2020-12-06T01:04:37 | {} | CONTRIBUTOR |
vuejs | docs | 724,684,540 | 686 | phanan | Please use our [forum](https://forum.vuejs.org/) or [Discord](https://vue-land.js.org/) for questions like this. Thanks. | 2020-11-10T12:56:22 | 2020-11-10T12:56:22 | {} | MEMBER |
vuejs | docs | 729,763,540 | 698 | skirtles-code | I've opened an issue against the main repo to get clarification about what the expected behaviour is:
https://github.com/vuejs/vue-next/issues/2633
I believe the TS definitions currently only allow `number | string` but, in my opinion, that's overly restrictive. If the TS definitions are updated then the docs can... | 2020-11-18T15:40:55 | 2020-11-18T15:40:55 | {} | CONTRIBUTOR |
vuejs | docs | 729,928,131 | 694 | skirtles-code | I don't use TypeScript myself but I've seen this question asked a lot. I haven't yet come across a proper answer.
Whatever the correct approach is, I think it would be worth documenting it in `typescript-support.md`. | 2020-11-18T20:16:02 | 2020-11-18T20:16:02 | {} | CONTRIBUTOR |
vuejs | docs | 734,963,008 | 668 | yyx990803 | This is now fixed in core. | 2020-11-27T19:36:37 | 2020-11-27T19:36:37 | {} | MEMBER |
vuejs | docs | 735,051,457 | 703 | NataliaTepluhina | @Derek-DZ I believe this is not a bug but an expected behavior: since Vue 3.0.0-rc.13 [watch APIs default to use `flush: 'pre'` instead of `flush: 'post'`](https://github.com/vuejs/vue-next/commit/49bb44756fda0a7019c69f2fa6b880d9e41125aa)
To achieve a desired (pre-rc.13) behavior, you can modify `watchEffect` in you... | 2020-11-28T07:36:31 | 2020-11-28T07:36:31 | {} | MEMBER |
vuejs | docs | 739,253,188 | 731 | skirtles-code | You need to change the `<my-count />` to `<my-count></my-count>`. Browsers don't support self-closing tags.
In future please post questions to the [Vue Discord chat](https://chat.vuejs.org/), the [Vue Forum](https://forum.vuejs.org/) or [Stack Overflow](https://stackoverflow.com/). This issues list is for reporting... | 2020-12-05T13:46:38 | 2020-12-05T13:46:38 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 740,765,365 | 723 | dev-itsheng | I have fixed them and added more explanation. | 2020-12-08T17:03:31 | 2020-12-08T17:03:31 | {} | CONTRIBUTOR |
vuejs | docs | 723,565,463 | 683 | nmezzopera | @NataliaTepluhina This is a first draft, I believe is quite rough and it needs some iteration to be presentable 😅
I was thinking that a boilerplate repository is probably a good addition ( as suggested by @JessicaSachs ) where such a repo should 'live' ? Shall I create it under my personal repositories or there is... | 2020-11-08T11:39:49 | 2020-11-08T11:39:49 | {} | CONTRIBUTOR |
vuejs | docs | 723,565,621 | 683 | nmezzopera | @znck Currently on my side I still have some quirks with the render functions, I was thinking to add this to a possible tips and trick section, but then I realised that RPV is still in beta ( I am still using the alpha ) so it probably does not make much sense to add things that are planned to be fixed ( or already fix... | 2020-11-08T11:41:21 | 2020-11-08T11:41:21 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 727,572,067 | 683 | znck | Typescript stuff can be done in a separate PR. 👍 | 2020-11-15T13:45:07 | 2020-11-15T13:45:07 | {} | MEMBER |
vuejs | docs | 730,350,318 | 698 | LongTengDao | I'm not sure that's a bug or feature, so I didn't ask in vue-next. I even have no idea it belong to Vue 2 / 3 / 2&3...
Problem more than restrictive is that, if support all these types, they will be use as it is, or stringify any type (except symbol) to string firstly?
I can study the soure, but I'm not sure ... | 2020-11-19T12:41:21 | 2020-11-19T12:41:21 | {} | NONE |
vuejs | docs | 731,098,271 | 561 | vutran6853 | I like add to the discussion. This statement `but kebab-case in templates and JSX` was under Vue 2 useage which is true. But in Vue 3 this will work work now still but in templates but not in JSX/TSX. In JSX/TSX it will throw error if it kebab-case.
Mybe we can add another example under **Good** for jsx?
```js
pro... | 2020-11-20T10:54:46 | 2020-11-20T10:54:46 | {
"+1": 2
} | NONE |
vuejs | docs | 731,950,522 | 618 | 7NZ | 
same.
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36
os Windows 10 pro
osVersion 20H2
| 2020-11-23T06:15:41 | 2020-11-23T06:15:41 | {} | NONE |
vuejs | docs | 734,391,197 | 383 | meteorlxy | Have implemented this PR in vuepress 2, as `@vuepress/plugin-docsearch`
> https://github.com/vuepress/vuepress-next/commit/ae5e45a157ecfed83401df64ca30ecffc5045341 | 2020-11-26T16:25:35 | 2020-11-26T16:25:35 | {} | MEMBER |
vuejs | docs | 734,690,933 | 715 | skirtles-code | It should be the same in Vue 3:
https://jsfiddle.net/skirtle/m0ng1cqf/
There was a conversation in #454 about documenting the removal of `$parent` but it appeared to be a misunderstanding, possibly caused by a bug. `$parent` still exists and it is documented in the API Reference.
I would note that the use of `... | 2020-11-27T07:34:21 | 2020-11-27T07:34:21 | {} | CONTRIBUTOR |
vuejs | docs | 739,089,918 | 722 | LongTengDao | > Do you have any confirmation that this is an intentional change and not just a bug?
Oh, I don't, it could be a bug. Let me ask. https://github.com/vuejs/vue-next/issues/2731 | 2020-12-05T00:29:04 | 2020-12-05T00:29:04 | {} | NONE |
vuejs | docs | 740,716,429 | 722 | NataliaTepluhina | Closing this issue as it's confirmed to be a bug on core repo. Please feel free to reopen if anything is not covered in docs after the fix for the mentioned bug is merged! | 2020-12-08T16:09:15 | 2020-12-08T16:09:15 | {
"laugh": 1
} | MEMBER |
vuejs | docs | 720,275,720 | 666 | u-sho | I checked with chrome.
If the issue depends on my environment, and if this PR looks bad on other's environment, sorry. | 2020-11-02T06:52:28 | 2020-11-02T06:52:48 | {} | CONTRIBUTOR |
vuejs | docs | 720,496,574 | 666 | phanan | Thanks for the effort, but I think this version is broken on Chromium browsers:
I'll go ahead and close the PR. Feel free to open another once the problem is actually fixed. | 2020-11-02T14:13:27 | 2020-11-02T14:13:27 | {} | MEMBER |
vuejs | docs | 725,343,107 | 687 | ArkIv | Thanks for the detailed answer.
And in the documentation (props), just add that the default will not be not reactive.
It may be confusing that we do not specify in Data reactive. | 2020-11-11T10:32:08 | 2020-11-11T10:32:28 | {} | NONE |
vuejs | docs | 729,494,634 | 693 | NataliaTepluhina | @skirtles-code @gtsiolis I agree with you both and I actually wanted to do this earlier but we had a link to the Migration guide promoted on Twitter/Evan's conference talks. I believe now we can safely move it to the separate section | 2020-11-18T07:34:54 | 2020-11-18T07:34:54 | {
"hooray": 1
} | MEMBER |
vuejs | docs | 733,710,752 | 711 | oebrab | Thanks! Learned a lot. | 2020-11-25T13:36:52 | 2020-11-25T13:36:52 | {} | NONE |
vuejs | docs | 743,073,593 | 740 | skirtles-code | Thanks. Always grateful for the scrutiny. I'd be happy to wait until next week if you want to let the weekend contributors have their opportunity. | 2020-12-11T09:14:04 | 2020-12-11T09:14:04 | {} | CONTRIBUTOR |
vuejs | docs | 721,542,450 | 478 | mandaputtra | Hello everyone, me and my friends on [@vuejs-id](https://vuejs.id/) will be translating the docs onto Indonesian. The repo is [here](https://github.com/vuejs-id/docs-next). We make use of [wei/pull](https://github.com/wei/pull) bot to keep track on the `master` branch so it automatically makes a pull request. Although ... | 2020-11-04T06:40:14 | 2020-11-04T12:09:32 | {
"eyes": 1
} | NONE |
vuejs | docs | 723,443,253 | 555 | sevillaarvin | I was wondering if SFC was deprecated in vue 3 since I didn't see it in the [provide/inject guide](https://v3.vuejs.org/guide/component-provide-inject.html). So I googled `single file component vue3` and this was the third result. Anyway I'm glad it's not deprecated. | 2020-11-07T12:58:01 | 2020-11-07T12:58:01 | {} | NONE |
vuejs | docs | 735,050,951 | 687 | NataliaTepluhina | Considering @skirtles-code point about complicated explanation and my own comments about how props `default` value is used, I don't think we need to add this to documentation. As I've mentioned above, you shouldn't override props default value from the child component (thus you don't need a reactivity), and when you pa... | 2020-11-28T07:28:55 | 2020-11-28T07:28:55 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.