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
Multiple bus but one locator ? #27
Comments
Sounds pretty reasonable to me. :) |
Great. Currently on holidays I will have a try when I will be back. |
On a related note, I got a request yesterday to be able to set an inflector per bus as well. Perhaps we should rejigger the build/config system a bit in general? But for now, ignore that and enjoy a well deserved holiday! 😄 |
I will start to work on it.
Same here, we need it ! |
Let's go on #29 |
Hi guys,
I wanted to keep using this great tactician to manage also my queries in addition to my commands.
So I decided to create a second bus as specified in the doc but I just realized that the locator still unique. So I cannot attach a handler to a specific bus ? All the buses could handle all commands ? I'm not fan.
Does it bothers someone that I make a PR to change this behavior ?
The tag would evolve in something like
We could also attach by default (no bus attribute specified) to all locators to keep BC if someone currently use same command through different buses.
Let me know if I miss something.
The text was updated successfully, but these errors were encountered: