-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Fix getEffectiveCheckNode
#60309
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
Fix getEffectiveCheckNode
#60309
Conversation
Looks like you're introducing a change to the public API surface area. If this includes breaking changes, please document them on our wiki's API Breaking Changes page. Also, please make sure @DanielRosenwasser and @RyanCavanaugh are aware of the changes, just as a heads up. |
@typescript-bot test it |
@gabritto Here are the results of running the user tests with tsc comparing Everything looks good! |
Hey @gabritto, the results of running the DT tests are ready. Everything looks the same! |
@gabritto Here they are:
tscComparison Report - baseline..pr
System info unknown
Hosts
Scenarios
Developer Information: |
@gabritto Here are the results of running the top 400 repos with tsc comparing Everything looks good! |
getEffectiveCheckNode
is currently used to adjust error position by skipping outer expressions of a node.This fixes the following problems in error position related to usage of
getEffectiveCheckNode
.Nested
satisfies
are not skipped:Playground
In JS files, JSDoc type assertions are skipped:
Playground
Found those problems when working on another PR.