Applications - Starlette

Creates a Starlette application.
Boolean indicating if debug tracebacks should be returned on errors.
A list of routes to serve incoming HTTP and WebSocket requests.
A list of middleware to run for every request. A starlette application will always automatically include two middleware classes. ServerErrorMiddleware is added as the very outermost middleware, to handle any uncaught errors occurring anywhere in the entire stack. ExceptionMiddleware is added as the very innermost middleware, to deal with handled exception cases occurring in the routing or endpoints.
A mapping of either integer status codes, or exception class types onto callables which handle the exceptions. Exception handler callables should be of the form handler(request, exc) -> response and may be either standard functions, or async functions.
A lifespan context function, which can be used to perform startup and shutdown tasks. This is a newer style that replaces the on_startup and on_shutdown handlers. Use one or the other, not both.
Non-negative maximum total size in bytes of an HTTP request body. The default, None, does not limit request body size.
Starlette includes an application class Starlette that nicely ties together all of its other functionality.
You can store arbitrary extra state on the application instance, using the generic app.state attribute.
Where a request is available (i.e. endpoints and middleware), the app is available on request.app.