-
Notifications
You must be signed in to change notification settings - Fork 274
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
Update the return types of the Customer Account API query #1537
Conversation
…n methods. Also change the Customer Account API to default to 2024-01.
const {data} = await context.customer.query<{ | ||
customer: {firstName: string; lastName: string}; | ||
}>(`#graphql | ||
}>(`#graphql:customer |
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.
👍💯 the previous example got me real confuse if customer
is being use because of graphql field name or as a key word for named graphel end point
Co-authored-by: Michelle Chen <michelle.chen@shopify.com>
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.
Local 🎩 is failing on the customer api example, but #1542 should fix it
WHY are these changes introduced?
We can't always assume there is a
data
property on the Customer Account API response. Also, the other properties,errors
andextensions
important and useful to the developer.WHAT is this pull request doing?
Return a complete response from the Customer Account API. Also change to 2024-01 as the default API version. Also, to prevent collisions on autocomplete/code gen with SFAPI, update the query comment to be
#graphql customer
HOW to test your changes?
Does the example still work?
Post-merge steps
Checklist