Facades... what is their purpose exactly?
Permalink
I'm switching from 5.6 and threw myself into the docs and the code on a live project.
These 'facades'... what is their purpose? I see they somehow insulate the developer from the fact if a particular object is a singleton or not, if a method is an instance method or a class member. Is this all? I feel like this is in connection with loose coupling of code even: if I am not mistaken, some sort of service locator pattern is working behind the scenes to locate the actual classes and pre-instantiated instances.
Do correct me if I am mistaken, or if there is anything else you feel you can add to help me have a better understanding!
These 'facades'... what is their purpose? I see they somehow insulate the developer from the fact if a particular object is a singleton or not, if a method is an instance method or a class member. Is this all? I feel like this is in connection with loose coupling of code even: if I am not mistaken, some sort of service locator pattern is working behind the scenes to locate the actual classes and pre-instantiated instances.
Do correct me if I am mistaken, or if there is anything else you feel you can add to help me have a better understanding!
I've also been looking into facades. This helped explain what appeared to be static calls to methods that didn't appear to be static.
While I now understand a little more about them, a description of them and how they are used in concrete5 would be very helpful.
I believe that concrete5 5.7 uses modified Laravel facades.
This article helped me a bit.
http://fideloper.com/create-facade-laravel-4...