starlette

First check

• I added a very descriptive title to this issue.
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the FastAPI documentation, with the integrated search.
• I already searched in Google "How to X in FastAPI" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answ

We should create an extension that allows you to profile your request using https://github.com/joerick/pyinstrument

Should probably an argument that lets you specify the path for the profile report.

Example API:

schema = strawberry.Schema(
	Query,
	extensions=[
		PyInstrument(report_path="./my-report.html")
	]

Should add a section to the docs for third-party examples and guides using Mangum

We have a basic test for piccolo asgi new:

https://github.com/piccolo-orm/piccolo/blob/master/tests/apps/asgi/commands/test_new.py

It can definitely be improved though. As a minimum, we should read the generated file contents, and use ast.parse(file_contents) to make sure the file is valid Python code. We use a similar approach here:

https://github.com/piccolo-orm/piccolo/blob/e0f04a4

Add it in CI

As we are going to implement theming support in BitcartCC store, see bitcartcc/bitcart-store#319, we need to extend the API to allow storing css url.
CSS url for the theme is just an url which will be loaded by the frontend.
Ideally in the future we will allow to host css right on the server and use a permanent link to server storage, for that #161 and file storage support should be implemented

We should document how to integrate with various ASGI frameworks besides Starlette (relevant resources in parentheses):

• Starlette
• FastAPI
• Responder
• Quart
• Sanic (listeners ≈ ASGI lifespan event handlers)

~The first step would be to moving the current "ASGI sub-mounting" Starlette-specif

https://asgi.readthedocs.io/en/latest/specs/www.html#websocket-connection-scope

"subprotocols" key should be built from Sec-WebSocket-Protocol header value. Currently it's always empty.

        scope = {
            "type": "websocket",
            "headers": flatten_headers(headers),
            "path": path,
            "query_string": query_string_bytes,
            "root_path":

As evidenced by msgpack/msgpack#194, there still is no clear answer on the "proper" MIME type for msgpack. Fluent-bit's HTTP output plugin uses application/msgpack for the content-type instead of aapplication/x-msgpack, so the msgpack-asgi middleware doesn't attempt to unpack requests from fluent-bit POST's

It would be nice to have an 'auto apply' option in the filter sidebar.

When the option is disabled, the filters are applied by manually pressing the 'apply' button:

When the option is enabled, the 'apply' button is hidden, and when any of t