-
Notifications
You must be signed in to change notification settings - Fork 19
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
EstablishClaim returns a TypeError for null error object #13405
Comments
YourIT Ticket Number Product User Type CSS ID Urgency What was the user trying to accomplish? Issue Description Caseflow URL(s) Associated |
I clicked "close and comment" in error |
Connects #13405 ### Description The `handleDecisionPageSubmit` function was returning an error when the `error` object was null. Utilized optional chaining operator to check for existence of the error object to solve.
1 |
2 | |||||
3 | |||||||
5 |
8 | Why 2?
Why 3?
|
/app/containers/EstablishClaimPage/EstablishClaim.jsx at line 222:67 }
this.props.performEstablishClaimSuccess();
},
(error) => {
this.props.performEstablishClaimFailure();
const errorMessage = CREATE_EP_ERRORS[error.response.body.error_code] || CREATE_EP_ERRORS.default;
const nextModifier = this.validModifiers()[1];
if (error.response.body.error_code === 'duplicate_ep' && nextModifier) {
this.props.onDuplicateEP(nextModifier); Navigation:
|
Last seen 2 months ago, looks like the fix worked! |
EstablishClaim returns
TypeError Cannot read property 'error_code' of null
when the error object is null.https://sentry.ds.va.gov/department-of-veterans-affairs/caseflow/issues/7176
https://dsva.slack.com/archives/CHX8FMP28/p1581609716309200
The text was updated successfully, but these errors were encountered: