Hotfix: Ensure scaffolding is done before initializing the redirect controller #2514
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
This PR addresses an issue encountered when changing from editing an existing entity to creating a new one of the same type. In some workspaces, when users attempted to create a new entity, the
isNew
state, which should be set to true upon creation, was mistakenly retained as false from the editing state at first. This resulted in a redirect from the create URL back to the edit URL.To fix this, this PR ensures that the redirect controller is initialized after the scaffolding logic is complete. Since the scaffolding/create method is already async, it makes sense to await this so we first start observing the "isNew" state afterward. This way, we ensure that the state we observe is correct.
Types of changes