mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-04-05 05:56:42 +00:00
Code Issues 32 Releases Wiki Activity

Refs #31369 -- Improved hint message in NullBooleanField's deprecation warning.

Browse Source
This commit is contained in:
Paul Brown 2023-05-02 18:42:11 +00:00 committed by GitHub
parent 506f93f0c3
commit 3b62d8c83e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
django/db/models/fields/__init__.py
View File

@ -2248,7 +2248,7 @@ class NullBooleanField(BooleanField):
"NullBooleanField is removed except for support in historical "
"migrations."
),
"hint": "Use BooleanField(null=True) instead.",
"hint": "Use BooleanField(null=True, blank=True) instead.",
"id": "fields.E903",
}

2
docs/releases/3.1.txt
View File

@ -821,7 +821,7 @@ Miscellaneous
:class:`~django.db.models.expressions.RawSQL` instead beforehand.
* The ``NullBooleanField`` model field is deprecated in favor of
``BooleanField(null=True)``.
``BooleanField(null=True, blank=True)``.
* ``django.conf.urls.url()`` alias of :func:`django.urls.re_path` is
deprecated.

2
tests/invalid_models_tests/test_deprecated_fields.py
View File

@ -59,7 +59,7 @@ class DeprecatedFieldsTests(SimpleTestCase):
checks.Error(
"NullBooleanField is removed except for support in historical "
"migrations.",
hint="Use BooleanField(null=True) instead.",
hint="Use BooleanField(null=True, blank=True) instead.",
obj=NullBooleanFieldModel._meta.get_field("nb"),
id="fields.E903",
),