You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
Per Alex's comment on #2879, cat4 error messages should include the field name. The value has been hard-coded in as part of #2879's changes, but the string should dynamically insert the relevant field name (and/or the field's friendly name, if applicable) from the schema instead.
Acceptance Criteria:
Cat4 error messages include the field name and/or friendly_name, dynamically pulled from the schema stored alongside each record
Testing Checklist has been run and all tests pass
README is updated, if necessary
Tasks:
Get the field from the schema into CaseConsistencyValidator
robgendron
changed the title
Add dynamic field name and/or friendly name to cat4 error messages
Add dynamic field name to cat4 error messages
May 21, 2024
Description:
Per Alex's comment on #2879, cat4 error messages should include the field name. The value has been hard-coded in as part of #2879's changes, but the string should dynamically insert the relevant field name (and/or the field's friendly name, if applicable) from the schema instead.
Acceptance Criteria:
name
and/orfriendly_name
, dynamically pulled from theschema
stored alongside each recordTasks:
CaseConsistencyValidator
name
into the cat4 error message string. The error should stay the same. [Design Deliverable] Update error audit to include cat 4 plain language fixes #2968 covers research to update the string based on feedbackTANF-app/tdrs-backend/tdpservice/parsers/validators.py
Line 257 in c2c465f
Open Questions:
N/A
The text was updated successfully, but these errors were encountered: