-
Notifications
You must be signed in to change notification settings - Fork 9
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
QueryBus with FinalizeGuard enabled returns null #24
Comments
Why you think you misuse the query bus?
This works for me with FinalizeGuard enabled |
Hmm, can you show how you resolve deferred promise inside the finder class? |
|
I have removed everything and included just bare message bus and implemented this test: It has 3 tests:
Hmm, why does it fail in the last test? |
This is not about Laravel packag I'd say, so I am closing this issue. |
Hi, I am lost with
FinalizeGuard
and how to set it up properly. I am not sure if this relates to Laravel package or to MessageBus core.I enabled
FinalizeGuard
in prooph.php config file.But the result of the query returns null.
If I disable the
FinalizeGuard
then query returns valid result. So it led me into looking inside of theFinalizeGuard
code.Looking at 48 line: https://github.com/prooph/service-bus/blob/c239acfd43cf8eec577e30ce0aa7da86d87b6191/src/Plugin/Guard/FinalizeGuard.php#L48
It creates a new Promise and here it losts resolved result.
It seems that I misuse QueryBus. Can you suggest the right way of resolving Deferred object inside my QueryFinder which works with FinalizeGuard?
The text was updated successfully, but these errors were encountered: