starlette

We only have documentation for schema directives, we should document query directives, here's an example of how they work: https://github.com/strawberry-graphql/strawberry/blob/main/tests/schema/test_directives.py

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

It would be nice if there was a new clause which can be added to queries called callback.

For example:

def callback_handler(success, value):
    if success:
        print(f'The query was successful and returned {value}')
    else:
        print("The query failed")

Band.select().callback(callback_handler).run_sync()

The callback could be a function or coroutine, wh

Within a controller, I don't think you can find a url for another handler using starlette url_path_for.

A working example of it can be found over https://github.com/developmentseed/pg_mvt/blob/10fa599928fc96ea30fad63289e40e39e564845d/pg_mvt/factory.py#L66-L96

Checklist

• There are no similar issues or pull requests for this yet.

Is your feature related to a problem? Please describe.

Add auto link in relationship. As example: https://python-sqladmin.herokuapp.com/admin/address/details/1 to get user I need to go to table users, find user(no search). Please make user_id a link to users

Describe the solution you would like.

user_id is

Add flake8-isort to current flake8 configuration to remove the necessity of running isort on CI.

Would you like to contribute to BitcartCC on a regular basis in a team of people, discussing the best ways of implementation and learning something new?
You can join the BitcartCC team!
We are a team of volunteers maintaining this project in our free time.
I will guide you through project setup and answer all the questions to help you onboard

The project uses many different technologies so y

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

Hello!
Your project looks interesting. Please translate docs into English

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

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