fix: Prevent readFragment
from falling back to any
return types
#216
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.
Resolves #215
Summary
This prevents
readFragment(data)
from falling back toany
as a return type when no generic was passed. It also preventsreadFragment(document, data)
to evaluate toany
when an invalid document is passed. This already errored previously on thedocument
argument, but now also preventsany
from being returned.Set of changes
readFragment<DocumentType>(data)
from evaluating toany
whenDocumentType
is left outreadFragment(document, data)
from evaluating toany
, instead falling back tounknown
on invalid inputs