-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Provide/inject #48
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
Provide/inject #48
Conversation
# Conflicts: # src/.vuepress/config.js
- ancestor components don’t need to know which descendants use the properties it provides | ||
- descendant components don’t need to know where injected properties are coming from | ||
|
||
## Working with reactivity |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've started this chapter here but the more I work on it the more I think it should belong to Composition API. Maybe it would be a good idea to just state provide/inject is not reactive by default
and say that if you want to make it reactive, you should look into Composition API chapter Making provide/inject reactive
or something like this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel same, we can introduce to idea here and expand on reactivity on composition API section. However, in my opinion, the following section should be here and we can further link it composition API section.
@znck could you please take an early look at this? Any changes / additions are much appreciated! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks really good. I recommend we change text in default slot behaviour section, see comments.
- ancestor components don’t need to know which descendants use the properties it provides | ||
- descendant components don’t need to know where injected properties are coming from | ||
|
||
## Working with reactivity |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel same, we can introduce to idea here and expand on reactivity on composition API section. However, in my opinion, the following section should be here and we can further link it composition API section.
Co-Authored-By: Ben Hong <ben@bencodezen.io>
Co-Authored-By: Ben Hong <ben@bencodezen.io>
Co-Authored-By: Ben Hong <ben@bencodezen.io>
Co-Authored-By: Ben Hong <ben@bencodezen.io>
Co-Authored-By: Ben Hong <ben@bencodezen.io>
8d8305e
to
a861494
Compare
a861494
to
d2dfb57
Compare
@znck I've done some fixes, could you please give it another round of review? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great now!
Co-Authored-By: Rahul Kadyan <hi@znck.me>
Co-Authored-By: Rahul Kadyan <hi@znck.me>
Co-Authored-By: Rahul Kadyan <hi@znck.me>
I moved 'provide/inject' outside from
Handling edge cases
chapter