You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2021. It is now read-only.
It is an interesting concept to be able to control applications using the method binding. But currently, it is limited to use container calls. Why can't we use explicit contextual method binding outside of the constructor to be able to bind the implementation of one method to another without refactoring the app to use those calls?
@taylorotwell mentioned it is a bit complicated (see laravel/docs#4798) even with calls.
I think this would be very powerful if we had to maintain an application with a huge codebase and poor dependency management, Maybe there are some pitfalls that explain why it is still not implemented even in 2021 (requests of this functionality were at Laravel 5+)?
The text was updated successfully, but these errors were encountered:
michael-rubel
changed the title
Service Container | Contextual Binding of Methods
Service Container | Contextual Binding of the Methods
Jun 27, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello!
It is an interesting concept to be able to control applications using the method binding. But currently, it is limited to use container calls. Why can't we use explicit contextual method binding outside of the constructor to be able to bind the implementation of one method to another without refactoring the app to use those calls?
@taylorotwell mentioned it is a bit complicated (see laravel/docs#4798) even with calls.
I think this would be very powerful if we had to maintain an application with a huge codebase and poor dependency management, Maybe there are some pitfalls that explain why it is still not implemented even in 2021 (requests of this functionality were at Laravel 5+)?
The text was updated successfully, but these errors were encountered: