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

Get rid of the AbstractInvokeStrategy #152

Closed
prolic opened this issue Jan 13, 2017 · 3 comments
Closed

Get rid of the AbstractInvokeStrategy #152

prolic opened this issue Jan 13, 2017 · 3 comments
Assignees
Milestone

Comments

@prolic
Copy link
Member

prolic commented Jan 13, 2017

We should get rid of the AbstractInvokeStrategy, the only class extending it is the HandleCommandStrategy, so there is no need for this abstraction.

@prolic prolic added this to the 6.0 Release milestone Jan 13, 2017
@prolic prolic self-assigned this Jan 13, 2017
@codeliner
Copy link
Member

but the AbstractInvokeStrategy should make it easy to define a userland strategy (from the docs):

If your favorite convention is not there you can easily write your own invoke strategy by extending Prooph\ServiceBus\Plugin\InvokeStrategy\AbstractInvokeStrategy and implementing the canInvoke and invoke methods.

@prolic
Copy link
Member Author

prolic commented Jan 13, 2017 via email

@codeliner
Copy link
Member

ok

prolic added a commit that referenced this issue Feb 8, 2017
@prolic prolic closed this as completed Feb 9, 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