This repository has been archived by the owner on May 6, 2018. It is now read-only.
Give a guessable name for tactician services #5
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
Using the extension is way better than ignoring errors.
So that they can be directly used, instead of always going through the CommandBus/QueryBus abstractions. This is useful when dealing with things outside of the HTTP context.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
When handling things outside of the HTTP context, we might want to use tactician buses directly (since we don't need to deserialise the request data).
This PR makes it possible by postfixing the tactician services with
.inner, so if you passcommand_busandquery_busto the compiler pass' constructor you will be able to inject the buses into your services using the idscommand_bus.innerandquery_bus.inner.