Type safe improvements #489
Merged
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
kazupon
changed the title
kazupon
force-pushed
the
improvement/typesafe
branch
from
1361a77 to
0bec188
Compare
Closed
remaining tasks
|
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.
Summary
Target APIs
packages/core-base/*.tspackages/vue-i18n/src/composer.tspackages/vue-i18n/src/legacy.tspackafes/vue-i18n/src/vue.d.tspackages/vue-i18n/src/i18n.tscreateI18nuseI18nNotes
This PR is breaking change.
The API I/F provided by vue-i18n is unchanged, but the TypeScript type definition I/F has some breaking change.
If you are using TypeScript in your project, you will need to fix some things in 9.2 or later.
Resolve issues
closes #407
closes #382