fix: update variable type variance to bivariant #161
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.
Summary
I've updated the implementation of the
__apiType
method to shorthand method definition. This modification enables bivariance in the variable type.Details
Let's consider a function that takes a specific
TypedDocumentNode
with certain requirements. Assume this function,queryAnimal
, receives a Graphql query withAnimalQueryResult
as the return type andAnimalQueryVariable
as the argument type.Suppose
dogDocumentNode
has a narrower scope thanAnimalQueryResult
for the Return Type ({ name: string; id: string; age: number }
) and a narrower scope thanAnimalQueryVariable
for the Variable Type ({ id: string }
). As a result, it should be usable as an argument forqueryAnimal
. However, due to the Variable Type ofTypedDocumentNode
being a function argument, TypeScript conducts type checking contravariantly for the VariableType, making it ineligible as an argument.To create a bivariant function argument in TypeScript, the method needs to be defined as a Shorthand Definition.
References
TypeScript FAQ: Why are function parameters bivariant?
Typescript Repo: Strict function types #18654