Add TE fields to Form526 validation (vets JSON schema) schema
Scope of this ticket - The contract for all remaining fields being added as part of Toxic Exposure initiative
Current state - FE and BE use JSONSchema to validate
New state - FE needs to point to patterns to validate to decouple the JSON schema from FE changes
Tasks
[ ] Reference the contract between FE and BE for schema validation
[ ] Add TE fields to vets-json-schema (for BE validation).
[ ] Add LH Regex pattern for herbicides other locations and additional hazard's specify other exposure
[ ] Verify that FE and BE validation schema is compatible
[ ] Attached to a Milestone (when will this be completed?)
[ ] Attached to an Epic (what body of work is this a part of?)
[ ] Labeled with Team (product support, analytics-insights, operations, service-design, Console-Services, tools-fe)
[ ] Labeled with Practice Area (backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content)
[ ] Labeled with Type (bug, request, discovery, documentation, etc.)
Issue Description
Add TE fields to Form526 validation (vets JSON schema) schema Scope of this ticket - The contract for all remaining fields being added as part of Toxic Exposure initiative
Current state - FE and BE use JSONSchema to validate New state - FE needs to point to patterns to validate to decouple the JSON schema from FE changes
Tasks
Acceptance Criteria
Related links
[ ] Original spike story
How to configure this issue
product support
,analytics-insights
,operations
,service-design
,Console-Services
,tools-fe
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)bug
,request
,discovery
,documentation
, etc.)