Add GraphQL infrastructure #188
Merged
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
Adds an API for GraphQL requests, and a build script to autogenerate TS types from a GraphQL schema + GraphQL queries. The most commonly used GraphQL client seems to be Apollo, but I'm not convinced it's not overkill for this usecase. In order to keep the dependencies lightweight but also keep our options open in the future, I've instead written a simple shim compatible with the codegen intended for Apollo but not actually using Apollo as a dependency. Since the GraphQL API doesn't get called yet, this PR is fully backwards compatible.
Xiphoseer
approved these changes
Jun 16, 2024
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.
Adds an API for GraphQL requests, and a build script to autogenerate TS types from a GraphQL schema + GraphQL queries.
The most commonly used GraphQL client seems to be Apollo, but I'm not convinced it's not overkill for this usecase. In order to keep the dependencies lightweight but also keep our options open in the future, I've instead written a simple shim compatible with the codegen intended for Apollo but not actually using Apollo as a dependency.
Since the GraphQL API doesn't get called yet, this PR is fully backwards compatible.