mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-10 23:39:11 +00:00
Code Issues 32 Releases Wiki Activity

Refs #35859 -- Included Task backends in system checks docs.

Browse Source
This commit is contained in:
Jacob Walls 2025-09-17 09:21:40 -04:00 committed by nessita
parent 4fcc2883fa
commit 9334499f53
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/topics/checks.txt
View File

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