Form 4142: Remove providerFacility maxItems #975
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
raudabaugh
force-pushed
the
form4142-updates
branch
from
98cb2d2 to
f0fbcb6
Compare
powellkerry
approved these changes
Feb 20, 2025
stevenjcumming
requested changes
Feb 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New schema
PR #973 made an incorrect assumption that there should be a maximum of 5 items on
providerFacility, when in fact those items are stored in a PDF overflow page. This PR reverses that max limit.Please ensure you have incremented the version in
package.json.https://github.com/department-of-veterans-affairs/va.gov-team/issues/
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.