support primitive-object-intersection types (branded primitive types) #277
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.
returnValidationErrors()
typechecking fails when a property is a primitive-object-intersection type (typical case of branded type).returnValidationErrors()
refers totype SchemaErrors<S>
for typingsthe purpose of
type SchemaErrors<S>
as is:is to map
S
properties conditionally:if property
S[K]
isobject | null | undefined
maps toPrettify<VEList & SchemaErrors<S[K]>>
else (property
S[K]
is primitive) maps toVEList
the issue arises when property
S[K]
is a branded primitive type.Branded primitive types are typically an intersection of a primitive with an object holding the brand
(e.g.
type email = string & { [k in brand_prop_type]: unique symbol }
)type SchemaErrors<S>
mapping condition considers branded-primitive-types as object, mapping them incorrectly, and finally leading toreturnValidationErrors()
type errorsProposed changes
the issue is resolved by simply reversing the condition:
this way any primitive - even when intersected - is eagerly catched and properly managed, keeping logic unaltered
Related issue(s) or discussion(s)
This is an improvement of a previous PR
#273
re #