Closed Rarst closed 2 years ago
Love this. I would like to see types added, but otherwise this is 💯 !
I would like to see types added
Where do you think types could be improved? :) The inputs/outputs are very mixed...
Where do you think types could be improved? :) The inputs/outputs are very mixed...
Ah, I see that the typing is largely controlled by the interface, and that there are callable|string|array
types, which is annoying. Seems this is as good as it can get. 👍
@Rarst that looks great, thanks a lot!
Related disparity with Slim is closure callbacks not binding to container, see #52.
I think this is a very good thing 👍 no problem here.
@Rarst would you be interested that I add you as maintainer to this project? This is a non-trivial change, and I want to avoid being a blocker on any fix or other change like this in the future. There is no commitment, it's mostly to give you a bit more room.
would you be interested that I add you as maintainer to this project?
I don't mind, but I tend to hop around, that is things have most of my attention when I am actively messing with them for my needs. :)
Very sorry for the delay, thanks a lot for all the work!
name:method
).Fixes #51
Alternative to #70, I tried to not change constructor signature. Since interface extends the previously used one, backwards compatibility should be intact.
One implementation difference with upstream is that resolver there depends directly on container and can do container lookups. I would prefer to do that, but backwards compatibility issue, same as above.
Related disparity with Slim is closure callbacks not binding to container, see #52.
Includes unit tests for everything I could think of, but needs more people to look at. A lot of possible cases between all the syntaxes and contexts.