Add a guide for writing custom review request conditions.
Review Request #15071 — Created May 21, 2026 and submitted
This is a complete guide for writing custom review request conditions,
used for integrations and in the future other parts of the UI.It starts off with an education of what conditions are for and the main
components, and then walks through the types of condition choices and
customization options, the operators and customization for those, and
then working with value fields, followed by how to register condition
choices.
Built the docs. Checked for any obvious build or spelling errors.
Ran it through Claude to check for any code or writing issues.
| Summary | ID |
|---|---|
| 833c3ed033435cd655a7b08e6f4486ba9265a4fd |
| Description | From | Last Updated |
|---|---|---|
|
Typo: trying to matching -> trying to match |
|
|
|
I notice in other examples, you got rid of the gettext wrapping. |
|
|
|
This is missing a : Also, other similar lists in this doc are using paragraph mode (blank line between term … |
|
|
|
We haven't seen this before, we see it below. |
|
|
|
Can we put in a type hint for the generic here too (like we do in review-request-condition-choices-hook.rst) ? |
|
|
|
Wrapping is a little funky here. |
|
|
|
These are actually the same as Any/None, just renamed in this class. We should get rid of this line. |
|
|
|
This should be in an if TYPE_CHECKING block. Same for other examples in this change. |
|
|
|
One too many ===s here |
|
- Change Summary:
-
- Removed gettext usage from a code sample.
- Changed the
ConditionValueclass list to use paragraph mode. - Added a generic for
ConditionValueMultipleChoiceField, and documented it with a link to Python generics. - Fixed a reference to point further below.
- Fixed typos.
- Commits:
-
Summary ID 753ba0b93632e3bda8222becc6e98230a0220b78 7ea1ea6e93a1897d13cf1e85ce1d9519ccdd2053