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
[ ] Dynamically replace the field name into the cat4 error message string. The error should stay the same. #2968 covers research to update the string based on feedback
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:
nameand/orfriendly_name, dynamically pulled from theschemastored alongside each recordTasks:
CaseConsistencyValidatornameinto the cat4 error message string. The error should stay the same. #2968 covers research to update the string based on feedbackOpen Questions: N/A