mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-03 18:38:50 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Fixed #35358, Refs #35234 -- Renamed _check() methods to check() for constraints.

Browse source
This commit is contained in:
Mariusz Felisiak 2025-02-19 20:27:30 +01:00 • committed by GitHub
parent 86493307f9
commit 65c46d6932
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 19 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/releases/6.0.txt
View file

@ -177,7 +177,8 @@ Migrations
Models
~~~~~~
* ...
* :doc:`Constraints </ref/models/constraints>` now implement a ``check()``
method that is already registered with the check framework.
Requests and Responses
~~~~~~~~~~~~~~~~~~~~~~

20
docs/topics/checks.txt
View file

@ -130,18 +130,18 @@ The code below is equivalent to the code above::
.. _field-checking:
Field, model, manager, template engine, and database checks
-----------------------------------------------------------
Field, constraint, model, manager, template engine, and database checks
-----------------------------------------------------------------------
In some cases, you won't need to register your check function -- you can
piggyback on an existing registration.
Fields, models, model managers, template engines, and database backends all
implement a ``check()`` method that is already registered with the check
framework. If you want to add extra checks, you can extend the implementation
on the base class, perform any extra checks you need, and append any messages
to those generated by the base class. It's recommended that you delegate each
check to separate methods.
Fields, constraints, models, model managers, template engines, and database
backends all implement a ``check()`` method that is already registered with the
check framework. If you want to add extra checks, you can extend the
implementation on the base class, perform any extra checks you need, and append
any messages to those generated by the base class. It's recommended that you
delegate each check to separate methods.
Consider an example where you are implementing a custom field named
``RangedIntegerField``. This field adds ``min`` and ``max`` arguments to the
@ -195,6 +195,10 @@ the only difference is that the check is a classmethod, not an instance method::
# ... your own checks ...
return errors
.. versionchanged:: 6.0
In older versions, constraints didn't implement a ``check()`` method.
Writing tests
-------------