docs: clarify scoped slot examples#3427
Open
ubugeeei wants to merge 8 commits into
Open
Conversation
✅ Deploy Preview for vuejs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
I have some feedback from my friend about scoped slot documentation.
Some readers find the scoped slots examples difficult to follow because the parent/child relationship and the usage/definition sides are implicit.
This update makes the example flow more explicit by showing the parent component usage first, then the child component slot definition, matching the order used in the JavaScript function analogy below.
Changes
receivedPropsNote:
corepack pnpm typecurrently fails on an existing.vitepress/config.ts:795plugin type cast issue unrelated to this change.