Quart
Strawberry comes with a basic Quart integration. It provides a view that you can use to serve your GraphQL schema:
Options
The GraphQLView
accepts the following options at the moment:
-
schema
: mandatory, the schema created bystrawberry.Schema
. -
graphql_ide
: optional, defaults to"graphiql"
, allows to choose the GraphQL IDE interface (one ofgraphiql
,apollo-sandbox
orpathfinder
) or to disable it by passingNone
. -
allow_queries_via_get
: optional, defaults toTrue
, whether to enable queries viaGET
requests -
multipart_uploads_enabled
: optional, defaults toFalse
, controls whether to enable multipart uploads. Please make sure to consider the security implications mentioned in the GraphQL Multipart Request Specification when enabling this feature.
Extending the view
The base GraphQLView
class can be extended by overriding any of the following
methods:
-
async def get_context(self, request: Request, response: Response) -> Context
-
async def get_root_value(self, request: Request) -> Optional[RootValue]
-
async def process_result(self, request: Request, result: ExecutionResult) -> GraphQLHTTPResponse
-
def decode_json(self, data: Union[str, bytes]) -> object
-
def encode_json(self, data: object) -> str
-
async def render_graphql_ide(self, request: Request) -> Response
get_context
get_context
allows to provide a custom context object that can be used in your
resolver. You can return anything here, by default we return a dictionary with
the request. By default; the Response
object from Quart is injected via the
parameters.
Here we are returning a custom context dictionary that contains only one item called βexampleβ.
Then we use the context in a resolver, the resolver will return β1β in this case.
get_root_value
get_root_value
allows to provide a custom root value for your schema, this is
probably not used a lot but it might be useful in certain situations.
Hereβs an example:
Here we are returning a Query where the name is βPatrickβ, so we when requesting the field name weβll return βPatrickβ in this case.
process_result
process_result
allows to customize and/or process results before they are sent
to the clients. This can be useful logging errors or hiding them (for example to
hide internal exceptions).
It needs to return an object of GraphQLHTTPResponse
and accepts the execution
result.
In this case we are doing the default processing of the result, but it can be tweaked based on your needs.
decode_json
decode_json
allows to customize the decoding of HTTP JSON requests. By default
we use json.loads
but you can override this method to use a different decoder.
Make sure your code raises json.JSONDecodeError
or a subclass of it if the
JSON cannot be decoded. The library shown in the example above, orjson
, does
this by default.
encode_json
encode_json
allows to customize the encoding of HTTP and WebSocket JSON
responses. By default we use json.dumps
but you can override this method to
use a different encoder.
render_graphql_ide
In case you need more control over the rendering of the GraphQL IDE than the
graphql_ide
option provides, you can override the render_graphql_ide
method.