AB#226656 Error Cannot read properties of undefined Grievance ticket #4525
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several changes to improve the robustness of the
LookUpReassignRole
andReassignMultipleRoleBox
components by adding optional chaining to handle potential undefined values. The most important changes are:Enhancements to handle potential undefined values:
src/frontend/src/components/grievances/LookUps/LookUpReassignRole/LookUpReassignRole.tsx
: UpdatedinitialValues
to use optional chaining forindividualData.individual
to prevent errors whenindividualData
is undefined.src/frontend/src/components/grievances/ReassignMultipleRoleBox.tsx
: Added optional chaining forreassignDataDictByIndividualId[selectedIndividualToReassign.id].new_individual
to handle cases wherereassignDataDictByIndividualId[selectedIndividualToReassign.id]
may be undefined. [1] [2]Code cleanup:
src/frontend/src/components/grievances/ReassignMultipleRoleBox.tsx
: Removed an unnecessary blank line to improve code readability.