Information about parent-child migration when removing native modifier #54
Conversation
This file contains 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
As described in this GitHub issue comments: vuejs/core#4566 (comment) and suggested as a useful addition to the docs.
✅ Deploy Preview for eager-kowalevski-41f498 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
After running `pnpm install` locally. To fix err_pnpm_frozen_lockfile_with_outdated_lockfile
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR implements the documentation suggestion contained within this GitHub issue comment:
vuejs/core#4566 (comment)
It explains how to migrate both the parent and child components for the removal of
.native. In the Vue 3 migration build you also need to update the child to work with this change. This info is currently missing from the docs, but is well explained in the above GitHub comment. Therefore this PR does what is hopefully the obvious and helpful thing, and copies the comment into the docs.