-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Allow assignability of non-empty object to generic mapped type #32071
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
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
156 changes: 98 additions & 58 deletions
156
...rcularlyConstrainedMappedTypeContainingConditionalNoInfiniteInstantiationDepth.errors.txt
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My expectation was that when a mapped type
target
was instantiated with someT
with a constraint like{ x: number }
, eithergetConstraintTypeFromMappedType(target)
orgetIndexType(target)
would essentially give mekeyof { x: number }
. But instead, they both give me a fairly unhelpful index type for a generic object.So then I thought, “ah, maybe if I use the apparent type of the mapped type,” but in the test case I added,
getApparentType(target) === target
.My true intent was just to get a plain object type for that instantiation of that generic mapped type, at which point I think I could just call
isRelatedTo(source, plainObjectType)
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the constraint is
keyof U | "a" | "b"
,getLiteralTypeFromProperties
is going to ignore theU
-ness of thekeyof U
part, while thetargetConstraint
will keep it. We'd like to keep as akeyof (T extends Entity)
is different from akeyof (U extends Entity)
and needs to be recognized as such. Rather than the filtering usingfilterType
to calculatefilteredByApplicability
as we're doing now, it's actually probably best to useintersectTypes(targetConstraint, sourceKeys)
since the result is the overlapping keys (be they generic or not). Making the indexed access below with that intersection should then work dandily.In fact, it seems like this is all the changes needed to fix the issue (from
master
):There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, fantastic, that’s so much better 🙌