fix(registry): show ID status column on group form; keep empty status for registry-added IDs (#1110)#297
Conversation
There was a problem hiding this comment.
Code Review
This pull request updates the spp_registry module to display the ID status column (as a badge) and description on the individual form, ensuring soft-removed IDs are distinguishable. It also adds a help tooltip to the status field, bumps the module version to 19.0.2.1.3, and introduces corresponding unit tests. Feedback on the changes suggests removing internal ticket references (e.g., OP#1110) from the user-facing help text of the status field to keep tooltips clean and translation-friendly.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| status = fields.Selection( | ||
| [("invalid", "Invalid"), ("valid", "Valid")], | ||
| help=( | ||
| "Validity of this ID. Left empty for IDs added directly via the " | ||
| "registry UI (kept consistent across the system, OP#1110); set by " | ||
| "the ID-document change request flow — Valid on add, Invalid on " | ||
| "soft-remove." | ||
| ), | ||
| ) |
There was a problem hiding this comment.
The help attribute is user-facing and displayed as a tooltip in the UI. It is best practice to avoid including internal ticket references (such as OP#1110) or internal system implementation details in user-facing strings, as they are not meaningful to end-users and clutter translation files. Let's clean up the help text to be more concise and user-friendly.
status = fields.Selection(
[("invalid", "Invalid"), ("valid", "Valid")],
help=(
"Validity of this ID. Left empty for IDs added directly via the "
"registry UI; set by the ID-document change request flow — "
"Valid on add, Invalid on soft-remove."
),
)
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## 19.0 #297 +/- ##
==========================================
+ Coverage 68.23% 71.59% +3.36%
==========================================
Files 157 418 +261
Lines 13420 26774 +13354
==========================================
+ Hits 9157 19170 +10013
- Misses 4263 7604 +3341
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
Why is this change needed?
On the group form the registrant IDs list gave no way to tell a soft-removed (invalid) ID apart from a valid one. There was also inconsistency in how the ID status was set: IDs added directly through the registry UI were being defaulted in a way that diverged from the ID-document change-request flow.
How was the change implemented?
models/reg_id.py,views/individual_views.xmlupdated accordingly.New unit tests
Added
spp_registry/tests/test_reg_id.pycases covering the empty-status default for registry-added IDs and the status behaviour.Unit tests executed by the author
Module test suite (
spp_registry) passes locally.How to test manually
spp_registry.Related links
OP#1110