-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Breaking change: Depth limit now hit for some types in 4.3 #43877
Comments
cc @DanielRosenwasser fyi |
@RyanCavanaugh @DanielRosenwasser I have a repro for the issue. It's not very small but it's the smallest I could get. This works with 4.2 but not 4.3: |
I'll let @RyanCavanaugh re-triage if appropriate, but if there's a good general fix here, it might be good to bring it to 4.3. There might be limitations though, and we might have to consider this "Working as Intended" or "Design Limitation". |
Here's another repro (smaller than @dragomirtitian's): |
Bug Report
π Search Terms
Depth limit 4.3
π Version & Regression Information
β― Playground Link
π» Code
Happens in a large codebase, I am currently unable to reproduce. The new error appears when a complex mapped & conditional type is used
π Actual behavior
Multiple new:
error TS2589: Type instantiation is excessively deep and possibly infinite.
π Expected behavior
Type checks successfully as in 4.2
Note
I bisected and found that this PR is introducing this break. While the behavior outlined there seems to be a net improvement, maybe a solution that doesn't break existing types can be found? Or if not this should be outlined in the 4.3 release notes as a breaking change.
The text was updated successfully, but these errors were encountered: