GH-2064 BeforeConvertCallback should be applied after the RootAggrega… #2065
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.
Closes #2064
Hey @mp911de, @schauder.
After giving it a couple of tries, I've come up with this solution. The idea is to separate the
doInBatch
andsaveInBatch
. The reason is that indoInBatch
there is an implicit assumption, that theFunction
that accepts the entity to create anAggregateChange
will just create anAggregateChange
. But in case ofsaveAll
, there were a conditional logic also applied in theFunction
(like what change to create,UPDATE
orINSERT
).So, in case of any suggestions or question, feel free to reach out, thanks!