-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Some corrections seem to be needed in Reactivity in Depth section #524
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm looking into updating this now. I think there are a few other tweaks required to that section too, so it may take a few days to get this ready for PR. |
@skirtles-code Since you're working on it, found one more typo here. I'm not sure if you have seen it before, so here it is:
Suppose there should be |
@Brisstor Thanks. I'm going to change all the references to Despite the apparent lack of progress I am still working on this. There are a few kinks that are proving difficult to iron out. |
@skirtles-code Thanks, also I'll be grateful if you mention me after you finish this issue so I would be able to update Russian translation of that section. |
When I tried translating to Japanese, I noticed some points need to be corrected in the part of
How Vue Tracks These Changes
in Reactivity in Depth section.https://v3.vuejs.org/guide/reactivity.html#how-vue-tracks-these-changes
In the part above, I think we have to say about function trucking, however, it seems to be said about updating new value.
I think the function name is not
effect
buttrack
.The text was updated successfully, but these errors were encountered: