1 Proposal from me..
Lets define Helper Interface or abstract Helper and all Helpers to become Classes.
I will use the url_helper to explain my simple idea.
- Why to set class instead of the current functions ?
In most of the cases inside any helper all functions have common resources which they use.In our case we can see that most of the helper functions are using Config\App, \CodeIgniter\HTTP\URI and \CodeIgniter\Services. If its 1 class with a couple of methods the how PHP OOP idea which CI is following at first place will be kept.
- What will help that ?
With class it will be a lot easier to extend any of those helper methods. Directly CI\Helper\URI can be extended inside a App\Helper\URI accessing all the services which are prepared for the URI with really easy option to control those default methods which are used at many places at any app.
- Accessing in all app layers Helpers..
Helpers must be available at any place in the Apps so I think that both ways with new instance or static instance should be possible. The plus is that by this way some unnecessary code can be skipped. I mention that specially for Views as in all other places I don't see a reason to do that..
URI::base_url() is a little bit shorter then something as URI::instance()->base_url().
Any group of helpers usually has common services/resources or logic and that is the reason why they are grouped.
I believe that such groups should be merged into one Class which will share any common features fast and easy.
Such complains as too long namespaces are not realistic at least for me.. because those days Composer is used massive and there some libraries which are used have really long classname + namespace ..
Its absurd somebody to complain that he have to define what is he using at his own app..
Regards
