Skip to content
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

Closed
wants to merge 2 commits into from
Closed

[DD] Dispute Debt initial #33151

wants to merge 2 commits into from

Conversation

Dr-Pongo
Copy link
Contributor

@Dr-Pongo Dr-Pongo commented Nov 21, 2024

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?

  • 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?

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)

Testing done

Manual testing complete.

Screenshots

NOTE: these screenshots are initial implementation and do not represent the final product

Before
/introduction image
/personal-information image
/contact-information image
/select-debt image
/existence-or-amount/0 image
/dispute-reason/0 image
/review-and-submit image
/confirmation image

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
  • Linting warnings have been addressed
  • Documentation has been updated (link to documentation *if necessary)
  • Screenshot of the developed feature is added
  • Accessibility testing has been performed

Error Handling

  • 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?

@va-vfs-bot va-vfs-bot temporarily deployed to master/dd/97002/new-app-initial/main November 21, 2024 03:09 Inactive
OptionSelect
OptionSelect previously approved these changes Nov 21, 2024
Copy link
Contributor

@OptionSelect OptionSelect left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🚀

@Dr-Pongo Dr-Pongo added the digital-dispute Changes relating to Digital Dispute form - debt resolution team label Nov 21, 2024
@Dr-Pongo Dr-Pongo force-pushed the dd/97002/new-app-initial branch from 2a3ae9e to 592459d Compare November 21, 2024 19:54
@Dr-Pongo Dr-Pongo marked this pull request as ready for review November 21, 2024 19:58
@Dr-Pongo Dr-Pongo requested review from a team as code owners November 21, 2024 19:58
Copy link

@va-vfs-bot va-vfs-bot left a 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

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

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ESLint disabled here

Copy link

@va-vfs-bot va-vfs-bot left a 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 => {

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}`);

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sentry found

@va-vfs-bot va-vfs-bot temporarily deployed to master/dd/97002/new-app-initial/main December 2, 2024 18:45 Inactive
@Dr-Pongo
Copy link
Contributor Author

Dr-Pongo commented Dec 4, 2024

Closing, and going to reopen after a rebase and now that the vets-json-schema has been merged

@Dr-Pongo Dr-Pongo closed this Dec 4, 2024
@Dr-Pongo
Copy link
Contributor Author

Dr-Pongo commented Dec 4, 2024

New PR here:
#33332

@Dr-Pongo Dr-Pongo mentioned this pull request Dec 4, 2024
14 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
digital-dispute Changes relating to Digital Dispute form - debt resolution team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants