Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
The requirements sensor shows verbosity now in details.
Still it is disconnected from editing.
Proposed resolution
Show verbosity also when editing. Thus, keys to use for exclusion are visible.
This is similar to enabled modules sensor...
In the long term, we might want to add a pattern to always display the sensor run result when editing.
Remaining tasks
User interface changes
API changes
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | requirements_sensor-2402449-3.patch | 2.88 KB | ginovski |
| #3 | interdiff-2402449-1-3.txt | 1.16 KB | ginovski |
| #1 | requirements_sensor-2402449-1.patch | 1.73 KB | ginovski |
Comments
Comment #1
ginovski commented1. Added the table with keys and title of the requirements to the edit form.
2. The table is filtered, excluded requirements are not shown.
There is a lot of code repetition with the verbose output, not sure if there is some way to take it directly?
Fixed also a typo in this patch, (Seperate->Separate)
Comment #3
ginovski commentedFixed test and added setting in schema.
Comment #4
berdirWe need to make the existing test more specific to ensure that cron exists not inside the textarea and we need to add specific test to make sure we do add the new information.