-
Notifications
You must be signed in to change notification settings - Fork 211
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
rest api to graphql #333
Comments
You need to change codes manually until we can create some wrapper to convert the codes into graphql. It will need some time, We have until February 2025. Let's see what we can achieve by that time. |
Following |
any update sir ?? |
@way2enjoy2 |
Really struggling to migrate |
@way2enjoy2 @epoks7 |
That’s bad news. I don’t think that Shopify realises the impact deprecating the REST api is having on the codebase out there. We are going to have to review and updated 1,000s on lines of code as a result of this just to keep our apps working.Sent from my iPhoneOn 19 Jan 2025, at 12:31, Tareq Mahmood ***@***.***> wrote:
@way2enjoy2 @epoks7
As GraphQL requires to mention returning data columns, the auto-migration of code seems to be a cumbersome work to do, still not guaranteed that will cover all scenarios. So better we follow the Shopify guideline to migrate our code to GraphQL. Here is the Shopify guide for the migration: https://shopify.dev/docs/apps/build/graphql/migrate/libraries
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
They will break several apps. Graphql does not provide everything rest api
used to provide and they are breaking the basic rule of development if
something is working don't touch that. If they were depreciating then also
what was need to kill rest api. They could have just supported.
…On Sun, 19 Jan, 2025, 7:28 pm rancey, ***@***.***> wrote:
That’s bad news. I don’t think that Shopify realises the impact
deprecating the REST api is having on the codebase out there. We are going
to have to review and updated 1,000s on lines of code as a result of this
just to keep our apps working.Sent from my iPhoneOn 19 Jan 2025, at 12:31,
Tareq Mahmood ***@***.***> wrote:
@way2enjoy2 @epoks7
As GraphQL requires to mention returning data columns, the auto-migration
of code seems to be a cumbersome work to do, still not guaranteed that will
cover all scenarios. So better we follow the Shopify guideline to migrate
our code to GraphQL. Here is the Shopify guide for the migration:
https://shopify.dev/docs/apps/build/graphql/migrate/libraries
—Reply to this email directly, view it on GitHub, or unsubscribe.You are
receiving this because you are subscribed to this thread.Message ID:
***@***.***>
—
Reply to this email directly, view it on GitHub
<#333 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALC7AD2VARXK5UWSV62MJV32LOVQLAVCNFSM6AAAAABPTOS5WSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMBQHA3TEOJYGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
now shopify is reminding of using graphql instead of rest api
so this will be automatically cared by your code or we need to write ourself
if this is my code for shopify rest api
$productspp = json_encode($shopify->Product($prod_id)->get(),true);
what will be equivalent for graphql
The text was updated successfully, but these errors were encountered: