Setup graphql plugin #176
Merged
Setup graphql plugin #176
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Now we just need the build to go green 🤔 |
|
@awanlin it looks like it's defaulting to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We want to show Backstage's GraphQL capabilities and how GraphQL can be integrated into Backstage.
Queryable GraphiQL interface
GraphiQL with Schema Definition
Approach
[email protected]to the resolution because the GraphQL Backend uses a newer GraphQL version, but all other plugins are at 16.2.0. I checked backstage/backstage, and it uses 16.8.1; maybe it'll get upgraded in an upcoming release.