Closed core23 closed 2 years ago
I don't understand, according to the doc, it already exists:
Some part are already possible. I want to create reusable bundles, so you have zero configuration.
The services configuration is not located inside your config folder, it is inside a bundle.
Some part are already possible. I want to create reusable bundles, so you have zero configuration.
The services configuration is not located inside your config folder, it is inside a bundle.
I see ! Your example helps me. Nice idea !
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
HI @core23, this has been stale for some times. Do you still work on this feature ?
The ExtensionCompilerPass
is / was very clunky. I'll give it a new try this weekend after the most recent refactorings
Closing due to lack of interest
Feature Request
I would like to contribute a new feature which will extend the registration of admin extensions.
At the moment you could only apply admin extensions by defining an extension config: https://github.com/sonata-project/SonataAdminBundle/blob/3.x/docs/reference/extensions.rst#configuration or you could tag admin services with
global
ortarget
.My idea is to add new attributes (
extends
,implements
, ...) tosonata.admin.extension
. So that all admin which extend a specific interface / extend a specific class / ... would use the extension.