Opened 4 years ago

Closed 4 years ago

#32214 closed New feature (wontfix)

Add django.core.exceptions.NON_FIELD_ERRORS key to the settings

Reported by: Ömer Faruk Abacı Owned by: nobody
Component: Core (Other) Version: 3.1
Severity: Normal Keywords: non_field_errors, settings
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Ömer Faruk Abacı)

It would be a good addition to be able to change django.core.exceptions.NON_FIELD_ERRORS key in settings. It is being used when a django.core.exceptions.ValidationError is raised without specifying a key. In Django Rest Framework it is editable via settings and it would be good to have a consistent key for non field errors between Django and Django Rest Framework without needing to patch django.core.exceptions.NON_FIELD_ERRORS. Thank you in advance!

ref: https://www.django-rest-framework.org/api-guide/settings/#non_field_errors_key

Change History (2)

comment:1 by Ömer Faruk Abacı, 4 years ago

Description: modified (diff)

comment:2 by Mariusz Felisiak, 4 years ago

Resolution: wontfix
Status: newclosed

It seems niche and adding a new setting is always a bit controversial. You can start a discussion on DevelopersMailingList if you don't agree. We need to reach a strong consensus on ML before moving it forward. Please remember to describe your use case, consistency with DRF is not a reason for adding a new setting to Django.

Note: See TracTickets for help on using tickets.
Back to Top