docs/integrations/aiohttp.md
Strawberry comes with a basic AIOHTTP integration. It provides a view that you can use to serve your GraphQL schema:
import strawberry
import asyncio
from aiohttp import web
from strawberry.aiohttp.views import GraphQLView
from typing import AsyncGenerator
@strawberry.type
class Query:
@strawberry.field
def hello(self, name: str = "World") -> str:
return f"Hello, {name}!"
@strawberry.type
class Subscription:
@strawberry.subscription
async def count(self, to: int = 100) -> AsyncGenerator[int, None]:
for i in range(to):
yield i
await asyncio.sleep(1)
schema = strawberry.Schema(query=Query, subscription=Subscription)
app = web.Application()
app.router.add_route("*", "/graphql", GraphQLView(schema=schema))
web.run_app(app)
The GraphQLView accepts the following options at the moment:
schema: mandatory, the schema created by strawberry.Schema.graphql_ide: optional, defaults to "graphiql", allows to choose the
GraphQL IDE interface (one of graphiql, apollo-sandbox or pathfinder) or
to disable it by passing None.allow_queries_via_get: optional, defaults to True, whether to enable
queries via GET requestsmultipart_uploads_enabled: optional, defaults to False, 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.The base GraphQLView class can be extended by overriding any of the following
methods:
async def get_context(self, request: Request, response: Union[Response, WebSocketResponse]) -> Contextasync def get_root_value(self, request: Request) -> Optional[RootValue]async def process_result(self, request: Request, result: ExecutionResult) -> GraphQLHTTPResponsedef decode_json(self, data: Union[str, bytes]) -> objectdef encode_json(self, data: object) -> str | bytesasync def render_graphql_ide(self, request: Request) -> Responseasync def on_ws_connect(self, context: Context) -> Union[UnsetType, None, Dict[str, object]]By overriding GraphQLView.get_context you can provide a custom context object
for your resolvers. You can return anything here; by default GraphQLView returns
a dictionary with the request.
import strawberry
from typing import Union
from strawberry.types import Info
from strawberry.aiohttp.views import GraphQLView
from aiohttp.web import Request, Response, WebSocketResponse
class MyGraphQLView(GraphQLView):
async def get_context(
self, request: Request, response: Union[Response, WebSocketResponse]
):
return {"request": request, "response": response, "example": 1}
@strawberry.type
class Query:
@strawberry.field
def example(self, info: strawberry.Info) -> str:
return str(info.context["example"])
Here we are returning a custom context dictionary that contains only one item
called "example".
Then we can use the context in a resolver. In this case the resolver will return
1.
By overriding GraphQLView.get_root_value you can 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:
import strawberry
from aiohttp.web import Request
from strawberry.aiohttp.views import GraphQLView
class MyGraphQLView(GraphQLView):
async def get_root_value(self, request: Request):
return Query(name="Patrick")
@strawberry.type
class Query:
name: str
Here we configure a Query where requesting the name field will return
"Patrick" through the custom root value.
By overriding GraphQLView.process_result you can customize and/or process
results before they are sent to a client. This can be useful for logging errors,
or even hiding them (for example to hide internal exceptions).
It needs to return an object of GraphQLHTTPResponse and accepts the request
and execution result.
from aiohttp.web import Request
from strawberry.aiohttp.views import GraphQLView
from strawberry.http import GraphQLHTTPResponse
from strawberry.types import ExecutionResult
class MyGraphQLView(GraphQLView):
async def process_result(
self, request: Request, result: ExecutionResult
) -> GraphQLHTTPResponse:
data: GraphQLHTTPResponse = {"data": result.data}
if result.errors:
data["errors"] = [err.formatted for err in result.errors]
return data
In this case we are doing the default processing of the result, but it can be tweaked based on your needs.
decode_json allows to customize the decoding of HTTP and WebSocket JSON
requests. By default we use json.loads but you can override this method to use
a different decoder.
from strawberry.aiohttp.views import GraphQLView
from typing import Union
import orjson
class MyGraphQLView(GraphQLView):
def decode_json(self, data: Union[str, bytes]) -> object:
return orjson.loads(data)
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 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.
import json
from strawberry.aiohttp.views import GraphQLView
class MyGraphQLView(GraphQLView):
def encode_json(self, data: object) -> str | bytes:
return json.dumps(data, indent=2)
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.
from aiohttp.web import Request, Response
from strawberry.aiohttp.views import GraphQLView
class MyGraphQLView(GraphQLView):
async def render_graphql_ide(self, request: Request) -> Response:
custom_html = """<html><body><h1>Custom GraphQL IDE</h1></body></html>"""
return Response(text=custom_html, content_type="text/html")
By overriding on_ws_connect you can customize the behavior when a graphql-ws
or graphql-transport-ws connection is established. This is particularly useful
for authentication and authorization. By default, all connections are accepted.
To manually accept a connection, return strawberry.UNSET or a connection
acknowledgment payload. The acknowledgment payload will be sent to the client.
Note that the legacy protocol does not support None/null acknowledgment
payloads, while the new protocol does. Our implementation will treat
None/null payloads the same as strawberry.UNSET in the context of the
legacy protocol.
To reject a connection, raise a ConnectionRejectionError. You can optionally
provide a custom error payload that will be sent to the client when the legacy
GraphQL over WebSocket protocol is used.
from typing import Dict
from strawberry.exceptions import ConnectionRejectionError
from strawberry.aiohttp.views import GraphQLView
class MyGraphQLView(GraphQLView):
async def on_ws_connect(self, context: Dict[str, object]):
connection_params = context["connection_params"]
if not isinstance(connection_params, dict):
# Reject without a custom graphql-ws error payload
raise ConnectionRejectionError()
if connection_params.get("password") != "secret":
# Reject with a custom graphql-ws error payload
raise ConnectionRejectionError({"reason": "Invalid password"})
if username := connection_params.get("username"):
# Accept with a custom acknowledgment payload
return {"message": f"Hello, {username}!"}
# Accept without a acknowledgment payload
return await super().on_ws_connect(context)