Note: Delete the description statements, complete each step. None are optional, but can be justified as to why they cannot be completed as written. Provide known gaps to testing that may raise the risk of merging to production.
Are you removing, renaming or moving a folder in this PR?
[x] No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)
[ ] Yes, I'm removing, renaming or moving a folder
Did you change site-wide styles, platform utilities or other infrastructure?
[x] No
[ ] Yes, and I used the proxy-rewrite steps to test the injected header scenario
Summary
Initial commit for digital dispute, much is still needed to call it complete though!
This PR inlcudes:
Initial form.js
Some helpers
All new pages
Debt fetching
Prefill transform
Related issue(s)
Link to ticket created in va.gov-team repo
department-of-veterans-affairs/va.gov-team#97002
Sister PR in vets-api for prefill
department-of-veterans-affairs/vets-api/pull/19545
Testing done
Manual testing complete.
Screenshots
NOTE: these screenshots are initial implementation and do not represent the final product
Before
/introduction
/personal-information
/contact-information
/select-debt
/existence-or-amount/0
/dispute-reason/0
/review-and-submit
/confirmation
What areas of the site does it impact?
(Describe what parts of the site are impacted if code touched other areas)
Acceptance criteria
Quality Assurance & Testing
[ ] I fixed|updated|added unit tests and integration tests for each feature (if applicable).
[ ] No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
[ ] Browser console contains no warnings or errors.
[ ] Events are being sent to the appropriate logging solution
[ ] Feature/bug has a monitor built into Datadog or Grafana (if applicable)
Authentication
[ ] Did you login to a local build and verify all authenticated routes work as expected with a test user
Requested Feedback
(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?
Note: Delete the description statements, complete each step. None are optional, but can be justified as to why they cannot be completed as written. Provide known gaps to testing that may raise the risk of merging to production.
Are you removing, renaming or moving a folder in this PR?
Did you change site-wide styles, platform utilities or other infrastructure?
Summary
Initial commit for digital dispute, much is still needed to call it complete though! This PR inlcudes:
form.jsRelated issue(s)
Testing done
Manual testing complete.
Screenshots
NOTE: these screenshots are initial implementation and do not represent the final product
/introduction/personal-information/contact-information/select-debt/existence-or-amount/0/dispute-reason/0/review-and-submit/confirmationWhat areas of the site does it impact?
(Describe what parts of the site are impacted if code touched other areas)
Acceptance criteria
Quality Assurance & Testing
Error Handling
Authentication
Requested Feedback
(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?