v1: Provide event naming strategies #1062
Merged
Conversation
This file contains hidden or 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
…instead of EventFlowConfiguration
rasmus
requested changes
Dec 6, 2024
Source/EventFlow/Configuration/EventNamingStrategy/VoidStrategy.cs
Outdated
Show resolved
Hide resolved
Source/EventFlow/Configuration/EventNamingStrategy/NamespaceAndNameStrategy.cs
Outdated
Show resolved
Hide resolved
Source/EventFlow/Configuration/EventNamingStrategy/NamespaceAndClassNameStrategy.cs
Outdated
Show resolved
Hide resolved
… in EventFlowConfiguration, renaming of VoidStrategy to Defaultstrategy, using string interpolation in naming strategies
rasmus
approved these changes
Dec 8, 2024
|
❤️ |
|
I'll get this added, update release notes and released |
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.
Related to #907, might even close #907.
This PR provides the capabilities to EventFlow to apply naming strategies which can ensure that no collisions among events with the same class name but different namespaces occur.
There are a few built-in strategies, users can provide their own strategy by simply implementing the
IEventNamingStrategyinterface.The desired naming strategy needs to be registered to the DI container, otherwise a
ViodStrategyis registered as default, which represents the current naming strategy.Also, I added a simple and small README for the documentation.