-
Notifications
You must be signed in to change notification settings - Fork 16.2k
chore(wip): giving migrate-ts a shot #33667
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
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
Co-authored-by: Enzo Martellucci <[email protected]> Co-authored-by: Mehmet Salih Yavuz <[email protected]>
…superset-ui-core/src/components` (#33593)
|
Based on your review schedule, I'll hold off on reviewing this PR until it's marked as ready for review. If you'd like me to take a look now, comment
|
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.
A bit of a not-so-dry run for ts-migrate, wanted to see what it would look like.
tsc errors post execution is about 76, which is pretty manageable. If we all decide this is a positive step forward I don't mind fixing the 76 errors.
Main benefits with this approach:
@ts-ignoreto@ts-expect-errorwith specificity about the error that's expected (providing super useful metadata in-code).@ts-expect-errorwill fail once the issue is fixed, forcing us to clean up those comments. With@ts-ignore, it's common to keep those messages around even when they've been addressed, which isn't good. With the extra metadata, it's easier to grep for certain types of errors for instance, which is positive.NOTE:
Details ->