Editor: Fix error when creating new record #1061
Open
+210
−193
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.
Description
The goal of this PR is to fix the error when creating a new record. The same exception sometimes occurs when editing fields of a draft. A first commit ensures errors displayed via the
notifications.service
still to be logged to the console.The actual error is caused by the fact that the
EditRecordResolver
is called even when routing to/create
. This happens due to thenavigate['edit']
calls within the component. Both navigations have been removed:/create
. => This prevents the exception when creating a new record.uniqueIdentifier
with theresourceIdentifier
in the form. => This prevents the exception when editing fields of a draft.Note to reproduce: The issue occurs on the first access to
/create
after app reload. It starts with the second access to/create
or accessing/create
after/edit
.Screenshots
Quality Assurance Checklist
breaking change
labelbackport <release branch>
label