fix: change DeepPartial
to account for object union types & unknown
#11385
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.
From the previous enhancement to allow
unknown
to be compatible withDeepPartial
(#11333), it introduced an unintended bug, being incompatible with union types containing both object & non-object types. Although this was resolved in #11373, it again made the definition ofDeepPartial
incompatible with any types containingunknown
again.With a new proposed definition that should be able to handle such cases, I have added some test cases discovered throughout #11333 and #11373 as type tests along with the new definition. By using
ExtractObjects
to extract any type that extendsobject
from a potential union type, it successfully appliesDeepPartial
for such object types while supportingunknown
as well.