fix: FetchForWritng() async projection returns null if there are no additional events to apply #3084
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.
When applying events to update an async projection snapshot, existing behavior returns null instead of the snapshot if there are no events to apply.
From codegen:
Testing this has been a headache - I am clearly missing something when it comes to properly testing generated code. In theory the included test matches my applications code but does not reproduce the issue. Additionally the following other bugs are identified:
RebuildProjection
on a projection whose type is a nested class does not work due to the way the type name is compared to the registered projections.RebuildProjection
would block until the rebuild is done.