We need to add .. autosummary:: to pages that need it.
We also need to make sure that this tag renders smoothly.

Usage example: https://github.com/wemake-services/wemake-python-styleguide/blob/ba060dfd18606365d4c09545554b595fce025e79/wemake_python_styleguide/violations/best_practices.py#L16-L17
Docs: https://www.sphinx-doc.org/en/master/usage/extensions/autosummary.html

https://pypi.org/project/toml-sort/

Sometimes a websockets/subscription connection gets closed by the browser and trying to send a message fails, we have a catch all exception that sends the error via GraphQL (useful for resolver exceptions), but we need to handle websockets.exceptions.ConnectionClosedOK and terminate the subscription (a return should be enough).

https://github.com/strawberry-graphql/strawberry/blob/master/stra

Given the number of tools officially supported(tested) by nbqa is increasing with every release, should we create a separate section in the documentation to document usage of each tool supported by nbqa with some elaborate examples and recommended setting against each tool.

Suggestions are welcome!

When we define a class like this:

def func():
    ...

class MyClass:
    my_func = lambda self, arg: arg

# or
class MyAnotherClass:
    my_func = func

The coverage plugin will consider the my_func as coveraged without any tests.
This behavior is expected because for it the my_func is an attribute!

I think it will be great use the normal signature, this will en