Replies: 2 comments 2 replies
-
Yes, as @jkrzefski said we have to take a deeper look into the consequences. One thing I know for sure is, that if we implement this we have to do it right so we don't have to revert it at a later time (which should never be the answer). I spoke with @clue about this and he mentioned some conflicts that could come up, so I'll use this opportunity to ping him so he can go more into detail 😅 |
Beta Was this translation helpful? Give feedback.
1 reply
-
there is already a really powerful container/DI framework, why we do not use this? => https://github.com/symfony/dependency-injection |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I recently made a pull-request to allow auto-wiring of container-parameters without using the factory-callback method. Simply put, that would allow you to turn this:
into this:
This is accomplished by accepting string parameters as arguments in auto-wiring for services.
But as @SimonFrings mentioned, this feature might have unwanted side-effects. I am not able to grasp the entire impact of this change, so that's what this discussion is for. Maybe there can be name-collisions. Maybe some other issues may come up. Please let's discuss this here to find a conclusion and hopefully make everything easier for everyone.
Beta Was this translation helpful? Give feedback.
All reactions