AlexCLeduc

Prevent plugin dependencies in "omit" from causing already-imported warnings

4

I came across the same bug noted [in this comment](https://github.com/nedbat/django_coverage_plugin/issues/71#issuecomment-678193581) when using django plugin alongside both source/include _and_ omit would cause a bunch of already-imported warnings for the plugin's dependencies:...

Consider supporting promise-based dataloaders in v3

21

I know graphql-core dropped support for promises, but the author seems to think promise-support can be added via hooks like middleware and execution context (see response to my identical issue...

Support/help with promise-based resolvers

14

I think I have a good use-case for non-async, promise-based resolution. We are making django ORM from our dataloaders. We moved away from using async in django 3.0 because django...

My workaround is to call prefetch_permissions once per model type, which sounds pretty straightforward to integrate in django-guardian. If not, the docs should be more precise.

Hi, thanks for adding m2m support! We've been waiting for years to migrate from a messy custom versioning tool. I've noticed if a form containing some normal fields as well...

Full credit to https://github.com/flavors/django-graphiql-debug-toolbar/pull/27, just applied a nitpick in case this gets merged faster. Apologies if this is bad etiquette! We're excited to use new 4.4.6 features but don't want...