-
Notifications
You must be signed in to change notification settings - Fork 125
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
76692 - [FSR] - Use Assets New data BE data/calcs #29844
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.
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.
|
||
return await apiRequest(url, options); | ||
} 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( |
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
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.
}, | ||
}); | ||
} 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); |
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 => { |
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( |
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
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.
} catch (error) { | ||
Sentry.withScope(scope => { | ||
scope.setExtra('error', error); | ||
Sentry.captureMessage( |
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
Fixed merge conflicts from merging expenses endpoint implementation. |
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.
After looking at what we replaced and the feature flags, I'm not sure we need this calculation anymore! Especially once the streamlinedWaiverAssetUpdate
has been deprecated. The API returns total assets, and we're only looking at liquid for streamlined calculations
Summary
Replace local asset calculations with API response.
Related issue(s)
department-of-veterans-affairs/va.gov-team#76692
Testing done
Log into app, submit a streamlined long and full FSR.
Screenshots
What areas of the site does it impact?
FSR
Acceptance criteria
Quality Assurance & Testing
Error Handling
Authentication
#sitewide-public-websites
Slack channel for questionsRequested 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?