You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Particular/rabbitmq-transport-maintainers discussed this today. The solution we will go with is changing the parameter to type Func<string>, since it is not possible to pass the address and eventType at the time of the delegate invocation.
adamralph
changed the title
Exchange name convention for direct routing topology is never passed "address" or "eventType"
Exchange name convention for direct routing topology is incorrectly typed
May 23, 2017
The only time the user specified exchange name convention is invoked, it is passed
null
for both theaddress
andeventType
parameters -NServiceBus.RabbitMQ/src/NServiceBus.RabbitMQ/Routing/DirectRoutingTopology.cs
Line 48 in fc98f52
The proposed solution is to either remove the exchange name convention parameter, or make it a string -
NServiceBus.RabbitMQ/src/NServiceBus.RabbitMQ/Configuration/RabbitMQTransportSettingsExtensions.cs
Line 19 in fc98f52
Plan of attack
The text was updated successfully, but these errors were encountered: