-
Notifications
You must be signed in to change notification settings - Fork 65
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
Decorator error when command is triggering another command #22
Comments
Yeah, I’m running into this too. For instance when registering a user, I want to issue 3 commands:
This fails to work:
The decorators continue to survive the execution in the CommandBus. They really should be reset with each call to I’m going to see if I can ferret out the issue directly, but I would love to hear from @JeffreyWay on this one. |
humm the CommandBus should remove the decorator after excecute it. Another point to me is the result of decorators don't change the command object. I've expected the decorators to be transformers to. Am I missing something here? |
I found a solution. There is a bit of code duplication between the |
Hi,
I have the following logica in my app:
A command is creating a player which is firing a event which checks if the player already has an alias, if not it will create it using another command. The first command has a decorator. When the second command is firing it is also hitting the decorator given in the first command which should not happen.
Regards, Ronnie
The text was updated successfully, but these errors were encountered: