docs: add explanation for template-refs defineExpose before await #3097
Conversation
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
✅ Deploy Preview for vuejs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
NataliaTepluhina
approved these changes
Dec 9, 2024
szymonlicau
referenced
this pull request
in vuejs-translations/docs-pl
Dec 9, 2024
…097) * docs: template-refs defineExpose before await * Update src/guide/essentials/template-refs.md --------- Co-authored-by: Natalia Tepluhina <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of Problem
In the child component’s <script setup>, if defineExpose is called before an await operation, the parent component will not be able to access the exposed properties and methods.
refs
Proposed Solution
Add an explanation in the template-refs.md document to provide users with a workaround for this issue. If a PR later resolves this issue, update this document accordingly.
Additional Information
I spent several hours on this issue. If the document provides this solution, it will help many people