Supporting strong typed identifiers for aggregated projections #3438
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
Docs for strong typed identifiers and aggregates Assertion that the aggregate id needs to be nullable for Marten Can use string based strong typed identifiers with single stream aggregations wip: past async single stream projections, had to add LoadManyAsync support to document storage
jeremydmiller
force-pushed
the
strong-typed-id-aggregates
branch
from
1b9eb3b to
6c7ecba
Compare
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.
Docs for strong typed identifiers and aggregates
Assertion that the aggregate id needs to be nullable for Marten
Can use string based strong typed identifiers with single stream aggregations
wip: past async single stream projections, had to add LoadManyAsync support to document storage