-
Notifications
You must be signed in to change notification settings - Fork 2.7k
move AdditionalApolloLinkResultTypes into TypeOverrides
#12840
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
move AdditionalApolloLinkResultTypes into TypeOverrides
#12840
Conversation
🦋 Changeset detectedLatest commit: c6b67e9 The changes in this PR will be included in the next version bump. 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 |
✅ Docs preview readyThe preview is ready to be viewed. View the preview File Changes 26 new, 66 changed, 5 removedBuild ID: 7ea9eade22b84c255014efa5 URL: https://www.apollographql.com/docs/deploy-preview/7ea9eade22b84c255014efa5 |
commit: |
size-limit report 📦
|
| "@apollo/client": major | ||
| --- | ||
|
|
||
| If you use an incremental delivery handler, you now have to explicitly opt into adding the chunk types to the `ApolloLink.Result` type. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm good with this. Less magic and makes a ton of sense. Good change!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! I like the change to be more explicit! 🚢 it
This puts
AdditionalApolloLinkResultTypesin line with the other type overrides.