-
Notifications
You must be signed in to change notification settings - Fork 127
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
Ability to override apiVersion from graphql api client after its defined from shopifyApp (used in shopify-app-remix) #1889
Comments
Hi there 👋 I think this would be a good improvement. I am going to move this to the teams work backlog for the new year. |
@lizkenyon I've checked with the latest version and I confirm what I'm requesting is possible! Thank you for checking. I must've done something wrong on my first try |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
In here, you can see that the version of the client becomes hardcoded once the
shopifyApp
is declared once with the first version.shopify-app-js/packages/apps/shopify-app-remix/src/server/clients/admin/graphql.ts
Lines 16 to 20 in bb59d07
An example of this is the shopify remix template
shopify.server.ts
file, here:https://github.com/Shopify/shopify-app-template-remix/blob/465a566475badecfd81ccc56ceefd704e3a1a99b/app/shopify.server.ts#L10-L15
What we want to acheive is to have a default for most operations in provided by the shopifyApp config and then the ability to override it in the
graphql
client exported from the majority of the auth contexts.Like so:
As of today, I've tried and I can't get it to work, which leads me to believe that even if the
apiVersion
param is exposed by thegraphql
function's options, it's not passed down.The text was updated successfully, but these errors were encountered: