Skip to content

Provide ids for checks, turn duplicate-middleware into warning? #1102

Closed
@blueyed

Description

@blueyed
  1. there should be ids for the checks, so that they can be ignored easily

  2. I have not checked if I am affected by SQL panel in django 1.11 #986, but I have a valid use case for having the middleware in there twice: I want it as early as possible, but then also after AuthenticationMiddleware (for custom request.user checks). I would argue that this should be a warning instead, so that it does not fail hard to start runserver for example.

Code: https://github.com/jazzband/django-debug-toolbar/blob/27f8a70953aebbd4949dc34ef552ce441d463a40/debug_toolbar/apps.py#L49

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions