The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Problem/Motivation
The UI / workflow around checking fields is very tedious, especially for complex sites.
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | Screenshot 2026-07-16 at 4.57.20 PM.png | 154.97 KB | smustgrave |
| #4 | Screenshot 2026-07-16 at 4.57.12 PM.png | 182.63 KB | smustgrave |
Issue fork scanner-3364450
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 3364450-new-admin-form
changes, plain diff MR !108 - 3364450-improve-the-field changes, plain diff MR !103
Comments
Comment #2
smustgrave commentedComment #4
smustgrave commentedTook a crack at it with an opinionated approach for sure.
Comment #5
smustgrave commentedDisclosure used claude to fix the tests but it does look cleaner.
Comment #6
smustgrave commentedComment #9
smustgrave commentedRebased
Comment #10
damienmckennaThis is a good improvement, thank you.
A few minor items:
* I don't think the form classes need to include "Scanner" in their names, I think the names could be simplified.
* It might be worth naming the new path "entities" rather than "entity-scope", which is overly verbose IMHO.
* An empty hook_update_N() might be needed to force sites to rebuild the caches, so the new routes & menu items are picked up.
Comment #11
smustgrave commentedAll makes sense to me
Comment #12
smustgrave commentedDid points 2 + 3 but for 1 I actually looked around and most modules have the name of the module in the form name so don't think we should drop scanner but open to other suggestions.
Comment #13
smustgrave commented