- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 155
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
Support clientAwareness being undefined in Apollo Link context #212
Support clientAwareness being undefined in Apollo Link context #212
Conversation
Thanks for the PR! I did have it that way originally, but then the when adding code coverage realized it was never necessary when used with Apollo Client. I did try to research instances where it may be undefined in context, but couldn't find any examples so I removed the default. |
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.
Could you please add a test for this, so we can get back to 100% code coverage? Also, we need to add a changelog entry under "Patch".
81900d5
to
0beacb1
Compare
@jaydenseric All set :) |
0beacb1
to
aab6052
Compare
aab6052
to
a19b3b8
Compare
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.
🙌
This change has been published in v14.1.1 🚀 |
Just a small tweak that ensures
createUploadLink
doesn't break ifclientAwareness
is undefined.clientAwareness
will always be defined when using a link through an ApolloClient instance, but may be undefined in other contexts (like if callingexecute
directly instead), so we shouldn't assume it will always be defined.