-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the 2122 and 2122a schema #949
Conversation
state_code: { type: 'string', minLength: 2, maxLength: 2 }, | ||
country: { type: 'string', minLength: 3, maxLength: 3 }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should I import enum
s of states and countries here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wrote a custom address object because the backend uses address_line1
, 2
, etc. Would it make more sense to use the existing hcaAddress
object and change the data handling on the backend?
What do you think @cosu419 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't think the state/country enums are necessary. hcaAddress
was copied from another schema and can probably be replaced.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved
New schema
This is an update to existing schemas for forms 21-22 and 21-22a.
Ticket: department-of-veterans-affairs/va.gov-team#93506
Please ensure you have incremented the version in
package.json
.Pull Requests to update the schema in related repositories
After you've merged your changes to vets-json-schema you'll need to make PR's to vets-website and vets-api. Please link them here.