I tried accessing some basic functionality with the App and it returned rejections saying the App was not authorized for blah-dee-blah.
Does this App in fact have all scopes enabled for it? If not, why not? If it does, and I should not be getting rejected, why am I getting rejected?
As an example, I tried a simple mutation on draftOrderCreate and was rejected as not having authority to do that. What?
Here you go..
I will guess that this is because my old trusty shop here which I have used well before Shopify even had an API, is not what you consider a "development" shop and so it fails for that reason?
If not, please do tell. And as an extra bonus, please turn on ALL scopes for that App for that shop...
Thanks. I'm able to replicate. The app should be requesting access to more scopes on installation.
I'll dig deeper to see what's up. In the mean time, consider running queries with an alternative app and your own key.
It's not like I cannot run queries! Of course I can do that, I use both code and Insomnia. As for the other proposed App, thanks, I will look into it. Ideally I would like the recipe for running QraphQL against a shop, with a key, inside my code editor, currently VSCode. That would be the best.
As for the Shopify tool failing, that is another matter, and I am glad that it was "not just me being me".
Just a note. I noticed a re-install on the Shopify App from your note. After re-installing, the App had the same lack of scopes problem. No biggy, I can wait till it is fixed.
The problem with the suggestion of the GraphiQL App is that it is not possible to set it for more than one shop. You have to manually setup the endpoint, and the access token header. So if I am working on 2 or more shops at once, and wish to run GraphQL queries against them, there is no easy way to manage that. Seems like an oversight but then again, whatever, it works. Just not suitable for busy developers with more than one fish to fry.
Another idea for these Apps would be to have them adopt some sort of idea of a pattern/template library. The amount of cut&paste one has to do to manage working with GraphQL is ridiculous. I should be able to call up a library of calls I have made in the past from across all my efforts, in order to keep development flow smooth. At this time, all the tools for GraphQL work remain kind of bush-league in this sense. All being so shiny and new I suppose, but not really.
Perhaps pass that on to the internal Shopify GraphQL App development team. A snippet library would be nice.
|24 seconds ago|
|2 hours ago|
|2 hours ago|