Request Context

Spry passes an Event object through handlers, middleware, and error handlers. This is the request context you actually work with.

What you will use most

• event.request
• event.params
• event.locals
• event.ws
• event.context
• event.method
• event.path

Params

Use event.params for file-routing values:

final id = event.params.required('id');
final slug = event.params.get('slug');

Helpers include:

• get(name)
• required(name)
• int(name)
• num(name)
• double(name)
• decode(name, decoder)
• $enum(name, values)

Locals

Use event.locals for request-scoped data shared across middleware and handlers:

Future<Response> middleware(Event event, Next next) async {
  event.locals.set(#requestId, DateTime.now().microsecondsSinceEpoch.toString());
  return next();
}

Runtime awareness

Use event.context.runtime.name when you need to surface or inspect the active runtime:

return Response.json({
  'runtime': event.context.runtime.name,
  'path': event.url.path,
});

Keep runtime awareness in responses or diagnostics. Routing itself should still be driven by the filesystem.

Websocket access

Use event.ws when a route may accept a websocket upgrade:

Response handler(Event event) {
  if (!event.ws.isSupported || !event.ws.isUpgradeRequest) {
    return Response('plain http fallback');
  }

  return event.ws.upgrade((ws) async {
    await ws.events.drain<void>();
  });
}

Read WebSockets for the route-level websocket model, runtime support, and handshake boundaries.