#686: Move Rule management functions to separate class #820
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
supereddie
requested review from
paolosalvatori,
SeanFeldman and
ErikMogensen
as code owners
ErikMogensen
approved these changes
Jan 7, 2025
SeanFeldman
approved these changes
Jan 10, 2025
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.
Part 04 of refactoring the ServiceBusHelper class #686. This is a fairly straight-forward 'move code to different class' to simplify the changes.
This part is moving Rules 'management actions' - that is, actions for Rules that need the
Microsoft.ServiceBus.NamespaceManagerto work, or add/remove actions on Rules which can only be done viaMessagingFactory.In addition:
RuleWrapperforServiceBusHelperEventArgs.EntityInstance, which in turn is used in various UI Controls