feat(core): add support for flush events #642
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There is a special kind of events executed during the commit phase (flush operation). They are executed before, during and after the flush, and they are not bound to any entity in particular. - `beforeFlush` is executed before change sets are computed, this is the only event where it is safe to persist new entities. - `onFlush` is executed after the change sets are computed. - `afterFlush` is executed as the last step just before the `flush` call resolves. it will be executed even if there are no changes to be flushed. Flush event args will not contain any entity instance, as they are entity agnostic. They do contain additional reference to the `UnitOfWork` instance. Closes #637
B4nan
added a commit
that referenced
this pull request
Aug 2, 2020
There is a special kind of events executed during the commit phase (flush operation). They are executed before, during and after the flush, and they are not bound to any entity in particular. - `beforeFlush` is executed before change sets are computed, this is the only event where it is safe to persist new entities. - `onFlush` is executed after the change sets are computed. - `afterFlush` is executed as the last step just before the `flush` call resolves. it will be executed even if there are no changes to be flushed. Flush event args will not contain any entity instance, as they are entity agnostic. They do contain additional reference to the `UnitOfWork` instance. Closes #637
B4nan
added a commit
that referenced
this pull request
Aug 9, 2020
There is a special kind of events executed during the commit phase (flush operation). They are executed before, during and after the flush, and they are not bound to any entity in particular. - `beforeFlush` is executed before change sets are computed, this is the only event where it is safe to persist new entities. - `onFlush` is executed after the change sets are computed. - `afterFlush` is executed as the last step just before the `flush` call resolves. it will be executed even if there are no changes to be flushed. Flush event args will not contain any entity instance, as they are entity agnostic. They do contain additional reference to the `UnitOfWork` instance. Closes #637
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There is a special kind of events executed during the commit phase (flush operation).
They are executed before, during and after the flush, and they are not bound to any
entity in particular.
beforeFlushis executed before change sets are computed, this is the onlyevent where it is safe to persist new entities.
onFlushis executed after the change sets are computed.afterFlushis executed as the last step just before theflushcall resolves.it will be executed even if there are no changes to be flushed.
Flush event args will not contain any entity instance, as they are entity agnostic.
They do contain additional reference to the
UnitOfWorkinstance.Closes #637