-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Throw on duplicate name in aggregate and event registry #611
Merged
DanielBadura
merged 2 commits into
3.1.x
from
throw-if-aggregate-name-duplicate-in-registry
Jul 3, 2024
Merged
Throw on duplicate name in aggregate and event registry #611
DanielBadura
merged 2 commits into
3.1.x
from
throw-if-aggregate-name-duplicate-in-registry
Jul 3, 2024
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
DanielBadura
force-pushed
the
throw-if-aggregate-name-duplicate-in-registry
branch
from
June 25, 2024 18:49
f6a67df
to
e50319a
Compare
…and throw if it is so Check if aggregateName is already in result set for the registry map and throw if it is so
DanielBadura
force-pushed
the
throw-if-aggregate-name-duplicate-in-registry
branch
from
June 25, 2024 18:50
e50319a
to
892421b
Compare
Hello 👋 here is the most recent benchmark result:
This comment gets update everytime a new commit comes in! |
DanielBadura
changed the title
Throw on duplicate name in aggregate registry
Throw on duplicate name in aggregate and event registry
Jul 3, 2024
DavidBadura
approved these changes
Jul 3, 2024
DanielBadura
force-pushed
the
throw-if-aggregate-name-duplicate-in-registry
branch
from
July 3, 2024 11:51
f37de16
to
0d54e10
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.
This will prevent configuration errors. Right now, we just take the last found Aggregate but imho we should throw since the name must be unique and this can not be the desired behaviour for our users.