Add the ability to use a custom backend. #9
Closed
Conversation
This file contains hidden or 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
|
Apparently a custom backend is also the preferred way to add caching of parsed queries, as per graphql-python/graphql-server#7 (see also #2) Since the desire to have cached parsing is popular, it would be nice to have a worked-out example of how to do that in our docs. |
6a8d7be to
21a6753
Compare
|
Thank you. This should be possible with #10 already. |
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.
From my point of view, the
backendis a good place to add some protection(e.g. query depth or complexity). In the custombackendit possible to analyze document AST and raise an exception, if the query does not comply with the rules before it will be executed.graphql_server.execute_graphql_requestaccepts the parameterbackendand if it None get default backend.