Async support for Django Graphql view

[ccsv]

As of Django 3.1 there is support for asynchronous views.

Can someone update the Django Graphql view to be asynchronous?

Also if I want my queries and mutations to be asynchronous what would be the best way of converting them? using the @sync_to_async decorator?

[rafalp]

We plan to move ariadne.contrib.django into separate library with Ariadne 0.14 release. Hopefully this feature request will see more attention when that happens.

[markedwards]

@kedlav Another thing I've worked on a bit is a way of implementing the equivalent of Django's @login_required and @permission_required for an Ariadne resolver. I'm not sure I've got a satisfactory solution yet, but I thought it might be in scope here.

[maxmorlocke]

We have a decorator we use for login_required. We'll be pushing enhancements like this up into the repo as soon as we get through the 0.0.1 release (e.g. get it into the repo and building with existing code). If you'd like to use ours, here's the source:

from rest_framework.exceptions import NotAuthenticated


def login_required():
    def wrapped_decorator(func):
        def wrapped(cls, info, *args, **kwargs):
            user = info.context["request"].user
            if not user.is_authenticated:
                raise NotAuthenticated()
            return func(cls, info, *args, **kwargs)

        return wrapped

    return wrapped_decorator

[maxmorlocke]

Alrighty, the initial port for ariadne_django is complete:

• https://pypi.org/project/ariadne-django/0.1.0/#description
• https://github.com/reset-button/ariadne_django

I've included some issues to make it clear what Lexria is committing to build into the package, with milestones going over our initial targeted enhancements. We're planning on porting our application to use ariadne_django in mid-April, but we welcome contributions and additional folks willing to help test. Should be entirely compatible with ariadne 0.13's contrib.django package (barring pathing changes) - minor code organization changes have been applied.

Thanks again @rafalp and team. Once Lexria's live with ariadne_django, I'll put in a pull request to the documentation site for ariadne to update the docs for 3rd party packages.

[markedwards]

Thanks @kedlav. Regarding async, I think I have some ideas on how to do it properly. Should I open an issue and plan to submit a PR for it?

[maxmorlocke]

Sounds good to me