runserver hangs forever, without log of error in console, in two cases

Hello, this is my first time posting, but I think bolstering django's error ouput system could be helpful as last week I spent a good amount of time debugging some issues related to django migrations 1. I began implementing DRF with DRF-Api-K

Re: Add a stable and documented setting to add files to the runserver watcher

In that case, I think we should at least start by documenting the ` *autoreload_started*` signal. Can I make a PR for the same? I think the best place to document this will be at https://github.com/django/django/blob/master/docs/ref/signals.txt On Monday, February 8, 2021 at 4:37:37 PM UTC+5:30 t

Re: Add a stable and documented setting to add files to the runserver watcher

Hey Diptesh! It was always my intention to document and expose the autoreloader signals to third party applications, that way ariadne can configure watches on the graphql files it knows about. I think this is preferable to having users having to configure this directly in their projects. We kept t

Re: Add a stable and documented setting to add files to the runserver watcher

Hi Diptesh The autoreload_started signal looks like the right approach. I see it's not documented but Django uses it internally for watching template and translation changes. I think it would be a good idea to document it. I don't think using the signal hacky, and it's not really a problem that it