Add new GraphQL API schemas #337
Closed
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
GMKrieger
force-pushed
the
feature/new-graphql-api
branch
from
f2b68f8 to
98cc55c
Compare
3 tasks
GMKrieger
force-pushed
the
feature/new-graphql-api
branch
from
98cc55c to
92ebe1f
Compare
|
Let's close this PR for the time being and focus on the database schema. |
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.
This PR is meant to be a place to discuss the possible changes for the API. It will not be merged as is, but rather is a way to share this change.
The new schemas were generated with PostGraphile, based on the node database. For more information on PostGraphile, you can access https://www.graphile.org/postgraphile/.
All inputs are welcome!