-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Provide variables and context to update function #7902
Conversation
e4e5eb9
to
6f8dc95
Compare
1d6167f
to
97f13ac
Compare
4ca6362
to
48a9af4
Compare
f19c622
to
f79c048
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.
Some initial thoughts from me, mostly related to the earlier discussion about default type parameters. Let me know if I can clarify anything!
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 to me!
With any large TS-related change like this, there's some risk of introducing type checking errors for developers using our exported types heavily, or in unusual ways. However, I think that risk is manageable because we're only merging this PR into release-3.4
, where it will get released in the next beta version. I'm also working on some v3.4 stuff that interacts with these types, so we'll have plenty of chance to exercise these changes before v3.4 is final.
Feel free to (squash and?) merge whenever you're ready.
Co-authored-by: Ben Newman <ben@apollographql.com>
Co-authored-by: Ben Newman <ben@apollographql.com>
This PR implements an enhancement discussed in #7843. A mutation's
update
function now receives an optional third argument with the context and variables provided to the original function.Checklist: