Publications in the Message Mapper Pipeline#3048
Merged
Merged
Conversation
iancooper
added
2 - In Progress
Breaking Change
v10
.NET
…from Command Processor; remove plural from bus name.
…rs to external service bus not Publication.
iancooper
requested review from
DevJonny,
holytshirt and
preardon
as code owners
DevJonny
pushed a commit
to DevJonny/Brighter
that referenced
this pull request
Feb 28, 2026
* Update the ADR for the Publisher Registry Issue * Move message mapper registry and transform factories to External Bus from Command Processor; remove plural from bus name. * Can construct instances of EventBus using ServiceProvider based Transform Factories * Simplify mapper pipeline choice * Expose Publication from Producer; move Outbox properties to EventBus configuration * Take a Publication into the MapToMessage method; move Outbox parameters to external service bus not Publication. * Pass Publication to Transform.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The Message Mapper Pipeline sometimes needs to access the metadata of the Publication, such as the Topic. This prevents us from creating a default message mapper, because we cannot access some fields which depend on the publication. In addition our support for CloudEvents is hampered by our inability to set metadata which is added to the header via CloudEvents such as Source and Subject. This naturally fits with the Publication but is again inaccessible. Whilst again, we could hard code this, we would continue to limit the ability to use a default mapper if we did that.