Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exchange name convention for direct routing topology is incorrectly typed #241

Closed
2 tasks done
adamralph opened this issue Oct 4, 2016 · 1 comment
Closed
2 tasks done
Assignees
Milestone

Comments

@adamralph
Copy link
Member

adamralph commented Oct 4, 2016

The only time the user specified exchange name convention is invoked, it is passed null for both the address and eventType parameters -

string ExchangeName() => conventions.ExchangeName(null, null);

The proposed solution is to either remove the exchange name convention parameter, or make it a string -

public static TransportExtensions<RabbitMQTransport> UseDirectRoutingTopology(this TransportExtensions<RabbitMQTransport> transportExtensions, Func<Type, string> routingKeyConvention = null, Func<string, Type, string> exchangeNameConvention = null)

Plan of attack

@adamralph adamralph added this to the 5.0.0 milestone May 23, 2017
@adamralph
Copy link
Member Author

@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 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
@adamralph adamralph removed this from the 5.0.0 milestone Sep 1, 2017
@adamralph adamralph reopened this Sep 1, 2017
@adamralph adamralph added this to the 5.0.0 milestone Sep 1, 2017
@adamralph adamralph self-assigned this Sep 4, 2017
@adamralph adamralph reopened this Sep 5, 2017
@adamralph adamralph removed their assignment Sep 12, 2017
@bording bording self-assigned this Sep 14, 2017
@bording bording closed this as completed Sep 21, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants