Symfony2 dependant Bundle configuration design

Question

The following question is not specific to SonataAdminBundle, the same design question remains for all third-parties Bundle, but I took a specific example to make it clearer.

I'm installing SonataAdminBundle for a new Symfony2 application, that will use extensively the Bundle (some kind of backend project).

I read on Sonata documentation (and on many other bundle doc too) that I should put the informations concerning the routing/config/services etc... on the application level, ie: app/config/XXX

However, I don't think it is the right approach in my project. In fact, my "BackendBundle" will be so dependant of SonataAdminBundle, that it won't be able to work without it.

Isn't it more logic to put all those configuration files directly in the Ressource folder of my own "BackendBundle", and not at the application ? In my mind, it is the role of my bundle to handle the Sonata config importation, and not the application role.

AdrienBrault · Accepted Answer · 2012-10-12 19:39:17Z

1

You can also put the routing configuration in a bundle, as soon as you import it from the main routing.yml file.

Bundle documentation use simple examples, to get setup quickly. This is why you'll see very often that way of importing routing resources.

answered Oct 12, 2012 at 19:39

AdrienBrault

7,7454 gold badges33 silver badges43 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

elwood Over a year ago

My idea was to @import Sonata config files into my own BackendModule (Which is a business specific project, and will never be reused for another project).

elwood Over a year ago

and then @import the config files of my BackendBundle at the application level. So this idea doesn't sound silly ? Is it the right approach in this case ?

fd8s0 · Accepted Answer · 2012-10-13 15:04:33Z

1

You should wire the service dependencies inside your bundle, however the actual configuration of the project belongs to the application.

It's perfectly acceptable for your bundle to be dependant in another bundle, however the configuration you add to it should be related to this dependency in particular and not to configuration itself. The actual configuration belongs to your application, adding project configuration to your bundle makes it effectively non-reusable.

edited Oct 13, 2012 at 15:04

answered Oct 12, 2012 at 23:57

fd8s0

1,9251 gold badge17 silver badges29 bronze badges

Collectives™ on Stack Overflow

Symfony2 dependant Bundle configuration design

2 Answers 2

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related