Add stricter typing to from
in useFragment
#11487
Draft
+21
−6
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.
Optimises the type to infer the __typename of the TypedDocumentNode that is passed in. I don't think you would ever pass in a different __typename but happy to be corrected.
I wasn't sure if the
TData extends { __typename?: string | undefined }
logic belonged within StoreObject itself so I added another type to contain that logic.Or possibly the type for
from
could be a Partial of TData?Checklist: