Emit nested action events after the transaction completes #14981
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
Fixes #11172 by storing a queue of nested
actionEvents
that gets emitted after the main transaction completes. The top level action event will be emitted, followed by the nested action events.Newly created nested items can be retrieved in the
action
event.The
database
in thecontext
is updated fromthis.knex || getDatabase()
togetDatabase()
as the emitting of action runs outside of the transaction now.Sample extension
Sample Flow
Type of Change
Requirements Checklist
If adding a new feature: