From 9334499f537e402ce5b92708209933045a8c5e7d Mon Sep 17 00:00:00 2001 From: Jacob Walls Date: Wed, 17 Sep 2025 09:21:40 -0400 Subject: [PATCH] Refs #35859 -- Included Task backends in system checks docs. --- docs/topics/checks.txt | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/topics/checks.txt b/docs/topics/checks.txt index 626f40a3b1..e22415e6d6 100644 --- a/docs/topics/checks.txt +++ b/docs/topics/checks.txt @@ -131,18 +131,18 @@ The code below is equivalent to the code above:: .. _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 piggyback on an existing registration. -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. +Fields, constraints, models, model managers, template engines, task backends, +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