We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Since Version 4, symfony recommends to not create any bundle to organize application logic.
So in a modern structure, AppBundle.php should be avoided.
AppBundle.php
WIthout it, I'm not able to register my additional backend assets with these helper methods (available thrue AbstractPimcoreBundle):
AbstractPimcoreBundle
getJsPaths
getCssPaths
getEditmodeJsPaths
getEditmodeCssPaths
Creating a AppBundle file just to use these methods is not a good way to go IMO.
AppBundle
Kernel.php
pimcore.static.js_paths
pimcore.static.css
config.yaml
What do you think?
The text was updated successfully, but these errors were encountered:
Why not use event listeners? https://pimcore.com/docs/pimcore/current/Development_Documentation/Extending_Pimcore/Bundle_Developers_Guide/Plugin_Backend_UI.html
https://github.com/pimcore/pimcore/blob/master/lib/Event/BundleManagerEvents.php
Sorry, something went wrong.
I completely missed that. Thanks!
No branches or pull requests
Since Version 4, symfony recommends to not create any bundle to organize application logic.
So in a modern structure,
AppBundle.php
should be avoided.Issue
WIthout it, I'm not able to register my additional backend assets with these helper methods (available thrue
AbstractPimcoreBundle
):getJsPaths
getCssPaths
getEditmodeJsPaths
getEditmodeCssPaths
Creating a
AppBundle
file just to use these methods is not a good way to go IMO.Possible Solutions
Kernel.php
?pimcore.static.js_paths
,pimcore.static.css
for example, placed inconfig.yaml
)?What do you think?
The text was updated successfully, but these errors were encountered: