[NFR]: Assets which respect the base static URI from \Phalcon\Mvc\Url
#16570
Labels
new feature request
Planned Feature or New Feature Request
\Phalcon\Mvc\Url
#16570
Hello,
I am just migrating from 4.2 to 5.6. I see there are a lot of fixes, features that I wanted to congrat your hard work.
Is your feature request related to a problem? Please describe.
I was using assets manager efficiently. But now I have to use it something like that. Removing universal prefix support was really necessary? We were already able to define external targets that we could add our own prefixes by calling url service or something like that. That felt me weird and wanted to know if there is a decent reason behind.
In Phalcon 4.2, the only requirement was defining the assets manager like below:
But now I have to define all the services in the outer scope of the service definition, which is not efficient because they'll create another instance even if I might not use them in the request.
Describe the solution you'd like
TagFactory
however, it requires strictly an argument which is not efficient if there are no any alternatives.TagFactory
also requires escaper instance which was annoyed that I might not need escaper at all.I've ended up by doing below way that it works:
That is not antipattern or something like that, right?
Mustafa,
Thanks.
The text was updated successfully, but these errors were encountered: