-
-
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
Remove traits if possible, simplify stack trace #2053
Comments
I floated the idea of removing Callable Resolver to it's own repo. Ideally it can be provided as a static or singleton class inside the DIC. There really isnt a reason for it being a trait. Moving it to it's own class should stop some of the jumping across the files. |
@geggleto I wasn't paying much attention to Slim when this was added, so I'm not 100% familiar with the internals of the current implementation. Can you walk me through it sometime soon on Slack? |
@codeguy Yeah, just ping me when you want to go through it. |
Maybe the trait should become a class and be composed into |
I think that a class |
Yes. This probably affects into the PSR-15 support that @bnf has started. |
Closed as per #2555 |
Will require more investigation.
The text was updated successfully, but these errors were encountered: