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 | 1,281,550,038 | 2,021 | devisasari | > Thanks for the fixes!
>
> I've reviewed the proposed changes and made a couple of suggestions below.
>
> On a separate note, you've opened a lot of PRs over the last few days, many of which contain the same commits. Some of the changes in this PR have already been merged, which just makes it extra work to revie... | 2022-10-17T22:02:42 | 2022-10-17T22:02:42 | {} | CONTRIBUTOR |
vuejs | docs | 1,282,241,756 | 2,040 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 59cf76529e5b3673c824d1c7c71b7feb4e8c78c8 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netli... | 2022-10-18T11:33:18 | 2022-10-18T11:34:35 | {} | NONE |
vuejs | docs | 1,282,668,072 | 1,994 | Saeed-Paris | @skirtles-code thanks for great tips. I really appreciate it. | 2022-10-18T16:28:35 | 2022-10-18T16:28:35 | {} | CONTRIBUTOR |
vuejs | docs | 1,282,956,122 | 2,032 | skirtles-code | Thanks for your work on the translation, but I think you've opened this PR against the wrong repo. This is the repo for the English documentation. | 2022-10-18T20:19:50 | 2022-10-18T20:19:50 | {} | CONTRIBUTOR |
vuejs | docs | 1,287,683,716 | 2,043 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 593bac8aad37443206f8ba7741f2f36591b156c1 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netli... | 2022-10-22T08:44:26 | 2022-10-22T08:45:38 | {} | NONE |
vuejs | docs | 1,288,180,042 | 2,046 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 0b23efa46f709d4a7abca930fa526b17400c8187 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netli... | 2022-10-23T19:18:43 | 2022-10-23T19:19:52 | {} | NONE |
vuejs | docs | 1,276,327,736 | 2,001 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 3db3c80c880a640570859a30ca251e7f4ab5f6b3 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netli... | 2022-10-12T15:01:52 | 2022-10-12T15:03:09 | {} | NONE |
vuejs | docs | 1,281,519,981 | 2,032 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 23df14043f8ccc2dbaf2b2c33e680b54d948c5cf |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netli... | 2022-10-17T21:30:09 | 2022-10-18T20:05:33 | {} | NONE |
vuejs | docs | 894,781,422 | 1,154 | NataliaTepluhina | @skirtles-code I'm reopening an issue so we're able to discuss the behaviour inside the `setup` | 2021-08-08T11:12:23 | 2021-08-08T11:12:23 | {} | MEMBER |
vuejs | docs | 896,341,735 | 1,160 | skirtles-code | I'm not sure what you're referring to here. Could you elaborate? | 2021-08-10T22:01:41 | 2021-08-10T22:01:41 | {} | CONTRIBUTOR |
vuejs | docs | 900,930,225 | 1,188 | skirtles-code | Thanks for the PR.
I believe this is only a problem for Linux users and it is caused by a problem with the fonts and CSS. We're currently working on migrating the docs to a new theme and it should be fixed as part of that, without needing any changes to the markdown files.
I'm using Linux myself so I understand h... | 2021-08-18T08:37:56 | 2021-08-18T08:37:56 | {} | CONTRIBUTOR |
vuejs | docs | 901,241,478 | 1,167 | yann-yinn | @bencodezen thanks for your anwser. I found a lot of answers by Evan inside this discusion https://github.com/vuejs/rfcs/discussions/378#discussioncomment-1158805 (thanks @edimitchel for the links).
I just understood that using **volar**, you should disabled **vetur** | 2021-08-18T16:09:02 | 2021-08-18T16:16:22 | {} | NONE |
vuejs | docs | 903,579,304 | 1,201 | JensVanhulst | @sodatea
Well it is not documented on the vue 3 docs as you can see below.
Isn't this confusing because if I'm on the vue site, I'm not going to follow the guide on vite ?
| 2021-08-23T09:04:08 | 2021-08-23T09:05:18 | {} | NONE |
vuejs | docs | 910,731,269 | 1,222 | skirtles-code | I wouldn't have expected `ModalWindow: () => import('./ModalWindow.vue')` to work in Vue 3, as functions are used to define functional components and not async components. That seems to be Vue 2 syntax.
Async components are loaded using `defineAsyncComponent`. This is documented in a few places, but here's the entry... | 2021-09-01T20:45:17 | 2021-09-01T20:45:17 | {} | CONTRIBUTOR |
vuejs | docs | 889,868,011 | 1,154 | zhenzhenChange | Our big brother on this side says that it is the `set` operation `xx.value=xxx` that blocks the current thread | 2021-07-30T12:44:25 | 2021-07-30T12:44:25 | {} | CONTRIBUTOR |
vuejs | docs | 889,959,534 | 1,154 | LinusBorg | 1. The adjustment of the docs to better describe how the current implementation works is still needed. I will leave this ticket here for that reason.
2. It sounds like you want to propose a different behaviour / additional "mode" for how `watch` behaves here. That should ideally not happen in a bug report, because the... | 2021-07-30T15:12:59 | 2021-07-30T15:12:59 | {
"+1": 1
} | MEMBER |
vuejs | docs | 896,440,823 | 1,165 | skirtles-code | For reference, the picture shows this section of the docs: https://v3.vuejs.org/guide/web-components.html#tips-for-a-vue-custom-elements-library
I'm not really familiar with the `customElements` API myself but it does seem that the method is called `define` and not `register`, https://developer.mozilla.org/en-US/doc... | 2021-08-11T02:02:11 | 2021-08-11T02:02:11 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 898,190,625 | 1,169 | wxsms | @NataliaTepluhina it's totally find. just a small question, thanks for your reply. | 2021-08-13T04:55:42 | 2021-08-13T04:55:42 | {} | MEMBER |
vuejs | docs | 899,550,117 | 1,148 | torressam333 | @skirtles-code sounds good! Thank you very much for getting back to me :). Ill keep my eyes open for any updates on this in the future. | 2021-08-16T14:19:14 | 2021-08-16T14:19:14 | {} | NONE |
vuejs | docs | 902,737,141 | 1,137 | orlyohreally | @skirtles-code, could you explain what you expect to be in the recipe a little bit more in terms of our recipe. Should we explain the logic behind the steps in more detail rather than jumping to examples? Or we need to explain something else in more detail?
> We also had concerns about a Cookbook entry that requires... | 2021-08-20T14:36:13 | 2021-08-20T14:36:53 | {} | NONE |
vuejs | docs | 906,540,682 | 1,210 | skirtles-code | Thanks for the PR!
I'm unclear what the purpose of the second change is. I believe the original wording is fine there.
I do agree that there's something not quite right with the first sentence, though I don't think just adding `an` fixes the problem. There are a few ways we could fix it. Personally, I think a bet... | 2021-08-26T16:01:46 | 2021-08-26T16:01:46 | {} | CONTRIBUTOR |
vuejs | docs | 906,730,118 | 1,154 | skirtles-code | @zhenzhenChange I'm going to attempt to fix this myself. I think I know why the code is currently written the way it is and roughly what changes need to be made. If it proves to be more complicated than I'm expecting then I'll open an issue in `vue-next` so that someone else can attempt it. | 2021-08-26T20:44:15 | 2021-08-26T20:44:15 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 889,866,279 | 1,154 | zhenzhenChange | Adding to our understanding, this round of timers, as long as the timing is the same, should all trigger at the same event loop, because its callback trigger criteria is time, and the time is the same, it will trigger at the same time.
[](https://imgtu.com/i/WX... | 2021-07-30T12:40:57 | 2021-07-30T12:42:47 | {} | CONTRIBUTOR |
vuejs | docs | 895,236,562 | 1,157 | yyx990803 | @bencodezen this should land on `master` since we are releasing 3.2 before we finish the new design. We will rebase `next` to include this. | 2021-08-09T13:46:18 | 2021-08-09T13:46:41 | {
"+1": 1
} | MEMBER |
vuejs | docs | 898,883,999 | 1,173 | Yukon123 | > When setting the attributes of a DOM element, Vue first checks whether there is a property on the element with the same name as the attribute. If there is, it will assign the value to the property rather than the attribute. In some cases, the browser will update the attribute when the property is assigned. In other c... | 2021-08-14T11:47:41 | 2021-08-15T12:53:45 | {} | NONE |
vuejs | docs | 899,301,835 | 1,162 | via-lars | Thank you very much for your passion and detailed explanation !
i think i understand.
let this issue be for your consideration to extend that doc part and close it at your leisure. | 2021-08-16T07:54:08 | 2021-08-16T07:54:08 | {} | NONE |
vuejs | docs | 903,685,076 | 263 | husayt | @CyberAP @NataliaTepluhina there is also another way to run multiple actions on the event handler. Many people, including myself, are still confused between the differences of the above and the below ways. It wil be great to clarify that in the same section.
```vue
<input v-on:input="(e) => { foo(); bar(e) }">
```
... | 2021-08-23T11:34:55 | 2021-08-23T11:37:02 | {} | NONE |
vuejs | docs | 906,127,856 | 1,203 | Yukon123 | @skirtles-code Thanks for reply.I believe it’s just my misunderstanding. | 2021-08-26T06:19:04 | 2021-08-26T06:19:28 | {
"+1": 1
} | NONE |
vuejs | docs | 906,711,058 | 1,154 | zhenzhenChange | Over the past two days I have been communicating with a friend about this issue and finally identified the problem.
---
First of all, I'm sorry that I didn't understand the `scope` in which this code was called at the beginning, so it caused unnecessary work for everyone. There are several reasons for this:
- ... | 2021-08-26T20:12:18 | 2021-08-26T20:17:41 | {} | CONTRIBUTOR |
vuejs | docs | 912,910,176 | 1,213 | NataliaTepluhina | Closing this PR as `key` is not required by the framework indeed. The warning is produced by ESLint plugin | 2021-09-04T05:16:27 | 2021-09-04T05:16:27 | {} | MEMBER |
vuejs | docs | 896,625,255 | 1,161 | NataliaTepluhina | We merged a MR to link to the styleguide so I believe we can safely close the issue now 🙏🏻 | 2021-08-11T08:39:41 | 2021-08-11T08:39:41 | {} | MEMBER |
vuejs | docs | 898,992,687 | 1,180 | skirtles-code | This issues list is for reporting problems with the Vue 3 documentation.
If you need help debugging a code problem then I recommend asking on [Vue Land Discord](https://chat.vuejs.org/). Alternatively, you could try asking on Stack Overflow.
Thanks. | 2021-08-15T04:12:29 | 2021-08-15T04:12:29 | {} | CONTRIBUTOR |
vuejs | docs | 902,627,211 | 1,195 | skirtles-code | Thanks for the PR.
I've only had chance to skim it so far, but I suspect this is the same problem that is described in https://github.com/vuejs/docs/issues/1154#issuecomment-894452072. I think this needs to be fixed in the code rather than the docs. It hasn't been forgotten, I just haven't had chance to attempt a fi... | 2021-08-20T11:28:32 | 2021-08-20T11:28:32 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 905,032,694 | 1,200 | skirtles-code | I believe the examples in the documentation are correct, though there are some considerations when adapting them to TypeScript:
https://v3.vuejs.org/guide/typescript-support.html#annotating-props
Maybe we should include the above link in that earlier guide? | 2021-08-24T23:04:19 | 2021-08-24T23:04:19 | {} | CONTRIBUTOR |
vuejs | docs | 905,358,198 | 1,195 | Yukon123 | @zhenzhenChange I edit my earlier reply,hope you can see my last version. | 2021-08-25T10:00:08 | 2021-08-25T10:00:08 | {} | NONE |
vuejs | docs | 899,009,477 | 1,137 | skirtles-code | We've decided that we'd like to take the Vue 3 Cookbook in a slightly different direction from the Vue 2 Cookbook. That is going to impact most of the Vue 2 recipes in some way and several of them are not going to be migrated because they're no longer a good fit for what we're hoping to create.
Going forward, we're ... | 2021-08-15T07:33:59 | 2021-08-15T07:33:59 | {} | CONTRIBUTOR |
vuejs | docs | 909,063,047 | 1,213 | wxsms | The error you mention should be from eslint, not from Vue. Actually, v-for does not required a key to be work. | 2021-08-31T09:27:05 | 2021-08-31T09:27:05 | {} | MEMBER |
vuejs | docs | 895,676,255 | 1,154 | zhenzhenChange | `v3.2.0` has been updated with `v-memo` and is one step closer to full body.
This issue of scheduling consistency is very important, hard work to everyone. | 2021-08-10T02:16:37 | 2021-08-10T02:16:37 | {} | CONTRIBUTOR |
vuejs | docs | 896,341,158 | 1,162 | skirtles-code | I'm not sure what change we can make to help clarify this.
Passing an object is covered here, in the section `Passing an Object`:
https://v3.vuejs.org/guide/component-props.html#passing-an-object
In that case, the child component would have a single prop with a `type` of `Object`. Using the `post` prop as an e... | 2021-08-10T22:00:24 | 2021-08-10T22:00:24 | {} | CONTRIBUTOR |
vuejs | docs | 897,349,613 | 1,167 | skirtles-code | The addition of the Composition API does pose a challenge from a documentation perspective. It allows projects to adopt significantly different styles and the documentation needs to negotiate that somehow. There's a certain amount of historical momentum in the Vue 3 docs and we're still working to try to address that. ... | 2021-08-12T05:00:49 | 2021-08-12T05:00:49 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | docs | 898,326,131 | 1,173 | Yukon123 | > @Yukon123 I noticed that you refer to Vue 2 docs here, just to make sure: what version of Vue you are using in the examples above? Attribute coercion behavior changed in Vue 3, here is an overview: https://v3.vuejs.org/guide/migration/attribute-coercion.html#attribute-coercion-behavior
@NataliaTepluhina I have cha... | 2021-08-13T09:30:29 | 2021-08-13T09:30:29 | {} | NONE |
vuejs | docs | 899,010,527 | 727 | skirtles-code | The Vue CLI documentation includes a section about deploying with Docker:
https://cli.vuejs.org/guide/deployment.html#docker-nginx
Our current feeling within the docs team is that there wouldn't be enough Vue-specific content to justify having a separate entry in the Vue 3 Cookbook. | 2021-08-15T07:45:42 | 2021-08-15T07:45:42 | {} | CONTRIBUTOR |
vuejs | docs | 890,271,248 | 1,154 | zhenzhenChange | 🤺🤺🤺🤺🤺 😁😁 | 2021-07-31T01:20:08 | 2021-07-31T01:20:08 | {} | CONTRIBUTOR |
vuejs | docs | 894,647,884 | 1,157 | bencodezen | @yyx990803 Should this PR be targeting `next` rather than `master`? | 2021-08-07T12:21:48 | 2021-08-07T12:21:48 | {} | MEMBER |
vuejs | docs | 894,781,139 | 1,158 | NataliaTepluhina | @skirtles-code is correct, this is intentional | 2021-08-08T11:10:20 | 2021-08-08T11:10:20 | {} | MEMBER |
vuejs | docs | 898,188,131 | 1,173 | NataliaTepluhina | @Yukon123 I noticed that you refer to Vue 2 docs here, just to make sure: what version of Vue you are using in the examples above? Attribute coercion behavior changed in Vue 3, here is an overview: https://v3.vuejs.org/guide/migration/attribute-coercion.html#attribute-coercion-behavior | 2021-08-13T04:45:57 | 2021-08-13T04:45:57 | {
"+1": 1,
"laugh": 1
} | MEMBER |
vuejs | docs | 899,018,839 | 461 | skirtles-code | @bencodezen Can this be closed now that the 3.2 docs have been merged? | 2021-08-15T08:58:52 | 2021-08-15T08:58:52 | {} | CONTRIBUTOR |
vuejs | docs | 902,627,984 | 1,193 | techandsoftware | Alright, I'll upgrade :) | 2021-08-20T11:30:15 | 2021-08-20T11:30:15 | {} | NONE |
vuejs | docs | 903,682,227 | 1,198 | NataliaTepluhina | @Yukon123 could you please explain why do you think it will be more precise? Binding on the element can be a property or an attribute, so I am not sure I understand why do we need to make this change. | 2021-08-23T11:30:01 | 2021-08-23T11:30:01 | {} | MEMBER |
vuejs | docs | 890,504,097 | 1,139 | NataliaTepluhina | Thank you for bringing your perspective here!
I agree a lot with @skirtles-code points and just want to add that we _intentionally_ left Options API as a default learning path and left Composition API to be an advanced feature. We may rethink this strategy if we see that community is widely adopting one API over an... | 2021-08-01T11:42:04 | 2021-08-01T11:42:04 | {} | MEMBER |
vuejs | docs | 898,206,036 | 1,173 | Yukon123 | > @Yukon123 I noticed that you refer to Vue 2 docs here, just to make sure: what version of Vue you are using in the examples above? Attribute coercion behavior changed in Vue 3, here is an overview: https://v3.vuejs.org/guide/migration/attribute-coercion.html#attribute-coercion-behavior
@NataliaTepluhina Thanks a l... | 2021-08-13T05:45:00 | 2021-08-13T06:07:44 | {
"+1": 1
} | NONE |
vuejs | docs | 904,622,497 | 1,197 | NataliaTepluhina | @Yukon123 thank you for the fixes! | 2021-08-24T13:04:08 | 2021-08-24T13:04:08 | {
"laugh": 1
} | MEMBER |
vuejs | docs | 905,297,592 | 1,195 | zhenzhenChange | @Yukon123 This is mainly a consistency issue, because you sometimes trigger `twice` and sometimes trigger `once`.
The same code, running in different environments at different moments, executes with different results, and consistency is not guaranteed.
---
`Twice`
[![fiKTHg.png](https://z3.ax1x.com/2021/08/0... | 2021-08-25T08:32:31 | 2021-08-25T08:32:31 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 906,481,279 | 1,209 | skirtles-code | Thanks for the PR!
I suspect the omission of `name` is actually intentional. Various options can be specified via a normal `<script>`, but this section of the docs seems to be trying to list only options where it is the recommended approach. For specifying a `name`, the recommended approach would be to name the file... | 2021-08-26T14:50:08 | 2021-08-26T14:50:08 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 913,078,130 | 849 | skirtles-code | There are some interesting cases involving `watch`.
Following on from [earlier](https://github.com/vuejs/docs/issues/849#issuecomment-774972883), properties accessed outside a reactive effect aren't tracked. The watch expression is a common source of this type of problem:
```js
watch(a.b, ...)
```
Assuming t... | 2021-09-05T03:14:29 | 2021-09-05T03:14:29 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 891,669,835 | 1,154 | zhenzhenChange | - Synchronization = Twice
- Synchronization within asynchronous functions = Once
- Two asynchronous functions, one `event loop` triggered = Twice
I don't want to use the `flush: "sync"` tag because it's not logical anymore | 2021-08-03T09:02:03 | 2021-08-03T09:02:03 | {} | CONTRIBUTOR |
vuejs | docs | 896,323,882 | 1,161 | skirtles-code | Thanks for the report.
Vue itself does not require the use of a `key` with `v-for`.
I believe the error you're seeing is coming from the Vue ESLint rules: https://eslint.vuejs.org/rules/require-v-for-key.html. These enforce best practices, usually based on the official style guide. The relevant style guide entry ... | 2021-08-10T21:20:48 | 2021-08-10T21:20:48 | {} | CONTRIBUTOR |
vuejs | docs | 896,631,331 | 1,162 | via-lars | `props: { myObject: Object }` resulted in a warning in the browser console for me and my template didn't render.
Using `<my-component v-bind="myObject"></my-component>`.
I intended to bind the object from the `data` `myObject` and not as a string.
But I see `myObject` is an attribute value, it "couldn't have" ... | 2021-08-11T08:49:12 | 2021-08-11T08:49:12 | {} | NONE |
vuejs | docs | 899,015,126 | 1,162 | skirtles-code | Using the `v-bind` prefix, or the `:` shorthand, makes Vue interpret the template attribute value as a JS expression. That expression is evaluated and the result is used as the actual attribute value. While DOM elements do typically require strings for their attribute values, the props for components can be objects or ... | 2021-08-15T08:23:46 | 2021-08-15T08:23:46 | {} | CONTRIBUTOR |
vuejs | docs | 903,547,439 | 1,200 | CNMathon | 
[Here](https://v3.vuejs.org/guide/component-props.html#prop-validation) is the location of the mentioned document. | 2021-08-23T08:18:43 | 2021-08-23T08:18:43 | {} | NONE |
vuejs | docs | 903,590,432 | 1,201 | haoqunjiang | So I'm not closing this PR but requesting you to document both npm 6 & npm 7 behavior.
Otherwise it will confuse npm 7 users. | 2021-08-23T09:17:53 | 2021-08-23T09:17:53 | {} | MEMBER |
vuejs | docs | 906,740,619 | 1,154 | zhenzhenChange | Ok, thank you, I can only focus on this matter, I do not have the ability to do the repair, hahaha. | 2021-08-26T21:02:58 | 2021-08-26T21:02:58 | {
"eyes": 1,
"laugh": 2
} | CONTRIBUTOR |
vuejs | docs | 912,910,520 | 1,220 | NataliaTepluhina | Thank you for your contribution! I believe the current version is more clear so I leave it as it is now | 2021-09-04T05:19:11 | 2021-09-04T05:19:11 | {} | MEMBER |
vuejs | docs | 913,351,565 | 1,222 | skirtles-code | I've now had chance to try this myself and it does appear to work as I suggested.
I think the existing documentation is sufficient. Using `defineAsyncComponent` is the correct way to create async components, whether or not you're using `<script setup>`. | 2021-09-06T05:19:08 | 2021-09-06T05:19:08 | {} | CONTRIBUTOR |
vuejs | docs | 896,613,676 | 1,161 | via-lars | Thank you!
Explicitly mentioning ESLint rules is outside the scope I concur.
Close this issue at your leisure. | 2021-08-11T08:21:59 | 2021-08-11T08:21:59 | {} | NONE |
vuejs | docs | 899,009,179 | 1,127 | skirtles-code | We've decided that we'd like to take the Vue 3 Cookbook in a slightly different direction from the Vue 2 Cookbook. That is going to impact the migration of most of the Vue 2 recipes in some way and several of them are not going to be migrated because they're no longer a good fit for what we're hoping to create.
Goin... | 2021-08-15T07:30:59 | 2021-08-15T07:30:59 | {} | CONTRIBUTOR |
vuejs | docs | 905,023,312 | 1,206 | ahsan-a | ahh, i must have missed that. Do you reckon it would still be a good idea to recommend volar alongside vetur? I haven’t yet came across something vetur can do that volar can’t do. | 2021-08-24T22:39:38 | 2021-08-24T22:39:38 | {} | NONE |
vuejs | docs | 915,470,607 | 1,232 | skirtles-code | Thanks for the suggestion, but I believe `specially` is the correct word in this context. | 2021-09-08T18:27:09 | 2021-09-08T18:27:09 | {} | CONTRIBUTOR |
vuejs | docs | 890,271,172 | 1,154 | zhenzhenChange | Ok ok, I understand, at the moment, it's a normal feature, if I need additional features then I need to go mention the feature request rfc, thank you for your patience in solving the problem | 2021-07-31T01:19:31 | 2021-07-31T01:19:31 | {} | CONTRIBUTOR |
vuejs | docs | 900,713,868 | 1,167 | bencodezen | Seconded on the things that @skirtles-code mentions.
We are certainly going through a bit of a challenge in how to embark with docs going forward as more paths open up for developers. That said, we appreciate you bringing up your concern and will keep this in mind as we keep iterating on the docs. Appreciate it @ya... | 2021-08-18T00:11:55 | 2021-08-18T00:11:55 | {} | MEMBER |
vuejs | docs | 900,937,517 | 1,189 | skirtles-code | Thank you for the PR but I believe the current documentation is correct.
The value `this.todos.length` would be reactive in Vue 3. But `provide` does not track changes, so if that number changes it will not be updated in descendent components that `inject` the value. | 2021-08-18T08:49:13 | 2021-08-18T08:49:13 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | docs | 905,836,335 | 1,203 | skirtles-code | The `nextTick` callback/promise shouldn't be called until all rendering is complete. So, to use your terminology, it should be after the next DOM update cycle is *finished*.
I'm going to close this, but if you'd like to share the example that led you to believe that the word *begin* was required then I'd be happy to... | 2021-08-25T20:05:58 | 2021-08-25T20:05:58 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 906,521,629 | 1,191 | skirtles-code | Thanks for the PR!
I think the current wording is correct, though potentially confusing.
In this context, an effect is considered invalidated when one of its reactive dependencies changes. An effect will not run again until it is invalidated.
I've opened #1211 to track this, as we do need to resolve the potent... | 2021-08-26T15:38:00 | 2021-08-26T15:38:00 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 912,911,421 | 1,217 | NataliaTepluhina | @sadn1ck thank you for reporting this! PRs are very welcome, would you mind creating one? 🙏🏻 | 2021-09-04T05:27:24 | 2021-09-04T05:27:24 | {} | MEMBER |
vuejs | docs | 774,990,762 | 849 | skirtles-code | **Update:** `props` does now include all props, even if they aren't passed. The problem described here does still exist, but it won't happen with `props`, which was the most common case.
---
This is already documented but `toRefs` will only work for properties that currently exist. `toRef`, on the other hand, can... | 2021-02-08T09:05:59 | 2021-09-05T02:11:42 | {} | CONTRIBUTOR |
vuejs | docs | 894,452,072 | 1,154 | skirtles-code | Interesting. If a `pre` watcher is triggered inside `setup` it runs immediately, skipping the scheduler queue.
The relevant section in the Vue code is here:
https://github.com/vuejs/vue-next/blob/1994f1200d12c05e509a812f2455de9da101c649/packages/runtime-core/src/apiWatch.ts#L347
```ts
if (!instance || instanc... | 2021-08-06T18:47:39 | 2021-08-06T18:47:39 | {} | CONTRIBUTOR |
vuejs | docs | 900,712,620 | 460 | bencodezen | @skirtles-code At the time, I was thinking that this would be better to have in the core docs, but I think this is something we can hold off for now since there is an official page. Thanks for the assist! | 2021-08-18T00:09:20 | 2021-08-18T00:09:20 | {} | MEMBER |
vuejs | docs | 905,030,117 | 1,206 | skirtles-code | Sorry, I may not have been clear. I believe the current reference to Vetur is incorrect and it should be changed to Volar, the same as the other places that make IDE recommendations.
Personally I don't use VSCode, so it is possible that I'm missing something, but I'm not aware of any circumstances where Vetur should... | 2021-08-24T22:57:50 | 2021-08-24T22:57:50 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | docs | 911,676,905 | 1,119 | danielkellyio | @skirtles-code just checking in on this to see if anything else needs to be done on my side before merge. Thanks! | 2021-09-02T13:21:44 | 2021-09-02T13:21:44 | {} | CONTRIBUTOR |
vuejs | docs | 914,693,303 | 1,224 | skirtles-code | We're currently in the process of migrating the docs to VitePress (on the `next` branch). I think there'll be some changes to the navigation as part of this, so it might be better to wait until after the migration is finished. | 2021-09-07T23:33:01 | 2021-09-07T23:33:01 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | docs | 914,930,733 | 1,230 | NataliaTepluhina | 1. `key` is introduced later in the tutorial and adding it to the Intro creates a cognitive overload
2. `key` is not required by the framework, only by the ESLint plugin | 2021-09-08T05:33:23 | 2021-09-08T05:33:23 | {} | MEMBER |
vuejs | docs | 898,431,452 | 1,178 | masx200 | I found that "@vue/reactivity" might be a better mobx. Developers can use "@vue/reactivity" in react as a global state manager!
It does not export the "watch" method, it has the "effect" method, which is not written in the documentation. | 2021-08-13T12:42:10 | 2021-08-13T12:42:47 | {} | NONE |
vuejs | docs | 899,981,907 | 1,173 | skirtles-code | This should now be fixed. `readonly` should be behaving like other boolean attributes as of Vue 3.2.3. Thanks for reporting the issue. | 2021-08-17T04:20:19 | 2021-08-17T04:20:19 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 903,599,968 | 1,201 | JensVanhulst | Should be fixed now. | 2021-08-23T09:30:05 | 2021-08-23T09:30:05 | {} | NONE |
vuejs | docs | 905,001,954 | 1,206 | skirtles-code | I believe this is an oversight. Elsewhere the docs were recently switched to recommending Volar:
* https://v3.vuejs.org/guide/typescript-support.html#editor-support
* https://v3.vuejs.org/api/sfc-tooling.html#ide-support | 2021-08-24T21:53:36 | 2021-08-24T21:53:36 | {} | CONTRIBUTOR |
vuejs | docs | 890,440,856 | 478 | dogia | How can I help to translate English -> Spanish? | 2021-08-01T03:14:58 | 2021-08-01T03:15:13 | {} | NONE |
vuejs | docs | 897,410,237 | 1,167 | yann-yinn | What an answer, thanks you so much @skirtles-code , your advices are super useful on thoses topics and your issue about reactivity is super interesting too.
Everything is subjective but it take so much times to explore by ourselves all the possible alternative, so recommendations feels very great.
So for someon... | 2021-08-12T07:24:11 | 2021-08-12T14:06:47 | {} | NONE |
vuejs | docs | 898,105,134 | 1,167 | skirtles-code | @yann-yinn From everything you've said, that does sound like an appropriate recommendation for your project.
The problems you're having in VSCode might be caused by the Vue ESLint plugin. I haven't experimented with it myself yet but I have seen other people mention a similar problem. Now that Vue 3.2 is officially ... | 2021-08-13T02:09:24 | 2021-08-13T02:09:24 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | docs | 898,188,554 | 1,169 | NataliaTepluhina | @wxsms thank you for your opinion! However, there are many other IDEs besides WebStorm and for some of them refactoring might be not that easy like in WS. I'd prefer to keep the current explanation in the styleguide. | 2021-08-13T04:47:29 | 2021-08-13T04:47:29 | {} | MEMBER |
vuejs | docs | 898,958,144 | 478 | milindanath | Hi,
I have started translating VueJs docs to Sinhala language today.
Repo: https://github.com/milindanath/docs-lk-si
Deployed to: https://v3-si-docs.netlify.app/
Please feel free to join if anyone interested.
| 2021-08-14T20:59:45 | 2021-08-14T20:59:45 | {} | NONE |
vuejs | docs | 900,710,575 | 295 | bencodezen | @skirtles-code nope! we can close this! | 2021-08-18T00:05:05 | 2021-08-18T00:05:05 | {} | MEMBER |
vuejs | docs | 902,491,823 | 1,193 | haoqunjiang | npm 7 requires the extra `--`. Though npm 6 doesn't. | 2021-08-20T07:24:36 | 2021-08-20T07:24:36 | {} | MEMBER |
vuejs | docs | 903,718,297 | 1,198 | Yukon123 | The MDN define attribute like https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes
>Elements in HTML have attributes; these are **additional values** that configure the elements or adjust their behavior in various ways to meet the criteria the users want.
Attribute are additional values to meet the criteri... | 2021-08-23T12:26:29 | 2021-08-23T12:26:29 | {} | NONE |
vuejs | docs | 903,796,498 | 263 | husayt | @NataliaTepluhina @CyberAP looking at the [test spec](https://github.com/vuejs/vue-next/blob/master/packages/compiler-core/__tests__/transforms/vOn.spec.ts), I notice that form with comma is not covered. So seems like what is currently recommended in documentation is not officially supported. only below forms are cover... | 2021-08-23T13:58:06 | 2021-08-23T13:58:34 | {} | NONE |
vuejs | docs | 912,911,032 | 1,206 | NataliaTepluhina | Thank you for reporting this! Changed Vetur to Volar 👍🏻 | 2021-09-04T05:23:57 | 2021-09-04T05:23:57 | {
"hooray": 1
} | MEMBER |
vuejs | docs | 912,912,692 | 1,217 | sadn1ck | Done @NataliaTepluhina, you can have a look. Thanks! | 2021-09-04T05:37:35 | 2021-09-04T05:37:35 | {} | NONE |
vuejs | docs | 892,835,869 | 1,158 | skirtles-code | I think this may be intentional. A 'kept-alive component' would be the child of a `keep-alive` component, not the `keep-alive` component itself. It could maybe be worded better but I don't think it would be correct to change 'kept-alive' to 'keep-alive'. | 2021-08-04T17:23:07 | 2021-08-04T17:23:07 | {} | CONTRIBUTOR |
vuejs | docs | 896,036,887 | 1,119 | danielkellyio | @skirtles-code all of the discussed revisions have been made and published to the courses. Thanks! | 2021-08-10T13:38:48 | 2021-08-10T13:38:48 | {} | CONTRIBUTOR |
vuejs | docs | 898,811,315 | 1,173 | skirtles-code | When setting the attributes of a DOM element, Vue first checks whether there is a property on the element with the same name as the attribute. If there is, it will assign the value to the property rather than the attribute. In some cases, the browser will update the attribute when the property is assigned. In other cas... | 2021-08-14T03:40:25 | 2021-08-14T03:40:25 | {} | CONTRIBUTOR |
vuejs | docs | 898,993,330 | 1,148 | skirtles-code | Thanks for your work on this and sorry for the delay getting back to you.
Usually a change like this would be integrated into the platform (i.e. VuePress) so we don't have problems maintaining it when we need to upgrade to the latest version. However...
We're currently in the process of migrating the docs from Vu... | 2021-08-15T04:22:14 | 2021-08-15T04:22:14 | {
"+1": 1
} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.