Support for Subscribe and Publish operations of the same Channel in different classes #91
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
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.
If a project tries to define Publish and Subscribe operations in different classes, with the nature of the
Channelsobject as a form ofDictionary<,>the document generator will find a conflicting key in the dictionary when performing the secondAddoperation, making it impossible to do this.With this change, a new
AddOrAppedoperation enables a Publish/Subscribe operation to be added to an existing Channel key if the existing one didn't have one defined, while still failing if multiple Publish or Subscribe operations are found for the same Channel.