-
Notifications
You must be signed in to change notification settings - Fork 126
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
[DD] Dispute Debt initial #33151
[DD] Dispute Debt initial #33151
Conversation
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.
LGTM! 🚀
2a3ae9e
to
592459d
Compare
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.
ESLint is disabled
vets-website
uses ESLint to help enforce code quality. In most situations we would like ESLint to remain enabled.
What you can do
See if the code can be refactored to avoid disabling ESLint, or wait for a VSP review.
} | ||
setSelectionError(null); | ||
}, | ||
// eslint-disable-next-line react-hooks/exhaustive-deps |
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.
ESLint disabled here
'ui:required': () => true, | ||
'ui:options': { | ||
labels: { | ||
// eslint-disable-next-line object-shorthand |
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.
ESLint disabled here
labels: { | ||
// eslint-disable-next-line object-shorthand | ||
EXISTENCE: EXISTENCE, | ||
// eslint-disable-next-line object-shorthand |
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.
ESLint disabled 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.
Sentry call found
Sentry captures a lot of data, and we want to make sure that we only keep information that will be useful for troubleshooting issues. This means that PII should not be recorded.
What you can do
Review your call to Sentry and see if you can reasonably reduce any information that is included, or wait for a VSP review.
debts: simplifiedResponse, | ||
}); | ||
} catch (error) { | ||
Sentry.withScope(scope => { |
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.
Sentry found
} catch (error) { | ||
Sentry.withScope(scope => { | ||
scope.setExtra('error', error); | ||
Sentry.captureMessage(`FSR fetchDebts failed: ${error.detail}`); |
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.
Sentry found
Closing, and going to reopen after a rebase and now that the vets-json-schema has been merged |
New PR here: |
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.js
Related issue(s)
[DD] Initial FE implementation va.gov-team#97002
[DD] Initial prefill for digital dispute vets-api#19545
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
/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
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?