Hello World example/'vscode-graphql.contentProvider' failed
See original GitHub issueI’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? 😃
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Hello World example/'vscode-graphql.contentProvider' failed
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...
Read more >Failed to find Content Provider in API 30 - Stack Overflow
The reason my custom ContentProvider doesn't work on Emulator with API 30 is Package visibility in Android 11+. To Fix my issue I've...
Read more >Content provider basics - Android Developers
A content provider manages access to a central repository of data. A provider is part of an Android application, which often provides its ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@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.
that link is only for the github graphql notebooks