Shopify Deprecating Rest API

[claridgicus]

Shopify is about to start committing to a full deprecation of the REST API, unless something drastically changes in the community.

They've started to kill the product and variant endpoints:
https://shopify.dev/docs/api/admin/migrate/new-product-model#whats-changing
This is just the beginning of incoming changes in the future which they will ultimately retire the entire REST API

With that in mind - just looking for some insight as to the future of the package, which I absolutely love and have used in many apps I've built, as to what the package will end up supporting / migration plans, how the package will pivot to the graphql endpoint for the majority of its REST calls.

I would prefer not to have to rebuild / perform a massive migration on every app that uses the package - but it's not like there will be much of a choice - I would like to be ahead of the curve myself as to not have a panic when they eventually end of life the endpoints and be able to roll out the changes quickly.

Any insight would be appreciated.

[Mr0nline]

@claridgicus the first reason I switched to this sdk instead of native one was because of the design of it and inbuilt retry and rate limit support, Although I do use this SDK for both REST and GraphQL calls, If Shopify ends up deprecating REST API, I guess we still can use this package for GraphQL but most of the REST methods will be redundant at this point!

[pliew]

I think this library would have tremendous value and importance if all the REST api methods are reworked to leverage GraphQL internally. If this could replicate the old REST calls then it would minimize code changes and development burden necessary to migrate an application.

Considering the vast amount of legacy apps, this would really benefit alot of people. Now the devil's in the details but it would be interesting if this would be possible.

[ikudosi]

I think this library would have tremendous value and importance if all the REST api methods are reworked to leverage GraphQL internally. If this could replicate the old REST calls then it would minimize code changes and development burden necessary to migrate an application.

Considering the vast amount of legacy apps, this would really benefit alot of people. Now the devil's in the details but it would be interesting if this would be possible.

Might be difficult and more expensive for the consumer as the design is different between the two end points. For GraphQL it's point-based and each property you select has it's own "cost". Unless you want the team to auto-assume you want everything?