-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
The actual callable is not passed to InvocationStrategy since introduction of DeferredCallable in Slim 3.2.0 #1785
Comments
The pull request #1783 would help to mitigate this, if accepted. I'd be able to retrieve the resolved callable and get its parameters using reflection. But really it would be better to call the custom InvocationStrategy from DeferredCallable instead of just passing arguments given to |
I am agree with @astax-t and I also use a custon InvocationStrategy. |
Having the same issue since 3.2 my auto wiring isn't working anymore. @irfanevrens i added a pull request on #1783 that now passes the resolvedCallable result to the foundHandler. Restoring the old behavior. |
Can you provide an example of code that's no longer working please? |
Sure. It's not the minimal code to replicate the problem, but pretty much copied from HttpFoundation:
But there is another PR to fix this problem. Maybe it's even better. |
Please test 3.x and let me know if this is now solved. |
Tested and is working correctly now |
Version 3.2.1 released now. Thank you very much for reporting this issue. |
Since introduction of
DeferredCallable
in Slim 3.2.0, the actual controller's callable is not given to the class implementing InvocationStrategy (the one set in$container['foundHandler']
)This makes it impossible to use reflection to find what are actual expected parameters.
I'm trying to use a custom
InvocationStrategy
that would match controller parameters names to route parameters - similar to the way it's done in Symfony HttpKernel. This was working in Slim 3.1.0, but not in 3.2.0.The text was updated successfully, but these errors were encountered: