Add stricter typing to from in useFragment

[samchungy]

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:

• If this PR contains changes to the library itself (not necessary for e.g. docs updates), please include a changeset (see CONTRIBUTING.md)
• If this PR is a new feature, please reference an issue where a consensus about the design was reached (not necessary for small changes)
• Make sure all of the significant new logic is covered by tests

[netlify]

‼️ Deploy request for apollo-client-docs rejected.

Name	Link
🔨 Latest commit	be233c9

[changeset-bot]

🦋 Changeset detected

Latest commit: 3952a5f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@apollo/client	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[phryneas]

Hi there, thanks for the PR!

Could you please give an example where this is useful?

From reading the code changes, I have a rough idea on the intent, but tbh., I have the feeling that this might break some use cases with unions and interfaces, so we'll have to be very careful here.