chore: bump ts to 4.8 #3654
Merged
chore: bump ts to 4.8 #3654
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
Signed-off-by: Sepush <sepush@outlook.com>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
4.8 is available but have some issue(have been fixed but did not realse) vuejs/core#6554 |
Codecov Report
@@ Coverage Diff @@
## main #3654 +/- ##
==========================================
- Coverage 62.91% 62.91% -0.01%
==========================================
Files 1058 1058
Lines 22002 22002
Branches 5746 5746
==========================================
- Hits 13843 13842 -1
+ Misses 6667 6665 -2
- Partials 1492 1495 +3
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
XieZongChen
approved these changes
Sep 2, 2022
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.
Signed-off-by: Sepush sepush@outlook.com
TypeScript(from 4.7) now enforces stricter checks that the given type is actually an object. As a result, values with the types unknown and never (and more rarely, just bare null and undefined) can no longer be spread into JSX elements.
https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-7.html#stricter-spread-checks-in-jsx
Unconstrained Generics No Longer Assignable to {}
https://devblogs.microsoft.com/typescript/announcing-typescript-4-8-beta/#unconstrained-generics-no-longer-assignable-to