Fix: Handle optional 'localized' and 'required' fields in DuplicateDocument component #8232
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.
Pull Request Description:
This PR fixes an issue in the
DuplicateDocumentcomponent where optional fields such aslocalized,required, andnamewere accessed without checks, causing potential errors.Since there is no backend endpoint to handle this, unlike in V3, the issue needs to be addressed in the frontend. This PR mirrors the behavior from V3 by safely checking for these optional fields before accessing them.
Key Changes:
localizedandrequiredare accessed only if they exist.namefield, preventing errors when it's not defined.This solution mimics V3 functionality and ensures robust duplication handling on the frontend in the absence of a backend solution.
Fixes #7270