Hello World example/'vscode-graphql.contentProvider' failed

[LinqLover]

I'm probably doing something very basic wrong, as I'm just learning GraphQL.

In VS Code, I created a .gql file with the following contents:

POST https://api.github.com/graphql
Authorization: bearer ghp_my0token0here

query($owner:String!, $name:String!) {
  repository(owner: $owner, name: $name) { 
    url, stargazerCount
  }
}

Then I run "Execute GraphQL Operations" via the Command Palette and receive the following error:

Running the contributed command: 'vscode-graphql.contentProvider' failed.

As said above, I'm probably doing something very basic wrong, but IMO this error message is not descriptive at all. Maybe you could give me a short hint what I am expected to do instead in order to test out my query from VS Code? :-)

[acao]

that seems to be an internal exception! I appreciate your humility, but this isn't what the error should look like at all. I specifically added a feature to display network and graphql errors in the results pane, so this is a bug/regression!

when you ran "execute graphql operation" command, was your cursor on or selecting the query?

[hinogi]

Same here
graphql notebook is working but not graphql operations

[acao]

hey! that functionality was removed for the time being in 0.4.x, if you see in the changelog. the latest merge removes that command from the manifest but there have been issues publishing it.

we no longer support query execution so as to limit the vscode-graphql maintenance/test surface area to focus on improcing the lsp experience

for now, we're suggesting joyce's extension in addition to ours, and considering creating a language bundle

[hinogi]

that link is only for the github graphql notebooks

[LinqLover]

If you cannot reproduce the issue, I would be willing to provide further information, but as mentioned by @hinogi, the command is no longer available and the suggested alternative works for notebooks only. It might be great to get this functionality back in any way. Please ping me if I can do anything else, and thanks for the feedback!

[acao]

@LinqLover we will eventually bring this functionality back via joyce's extension and/or another extension, once there are resources to support it.

For now, we need to focus on some significant changes and longstanding issues in the language server and thus the extension reference implementation. I and @orta debated it for a while but he is right, this is the most realistic path for us for now until we have more interested contributors to help.