Download the PHP package nucleos/sonata-auto-configure-bundle without Composer

SonataAutoConfigureBundle

Tries to auto configure your admin classes and extensions, so you don't have to.

This is a fork of the no longer maintained kunicmarko/sonata-auto-configure-bundle.

Documentation

• Installation
• Configuration
• How does it work
• Attribute

Installation

1. Add dependency with Composer

2. Enable the bundle for all Symfony environments:

Configuration

How does it work

This bundle tries to guess some stuff about your admin class. You only have to create your admin classes and be sure that the admin directory is included in auto discovery and that autoconfigure is enabled.

This bundle will tag your admin classes with sonata.admin, then we find all admin classes and if autoconfigure is enabled we take the class name. If you defined a suffix in the config (by default it is Admin) we remove it to get the name of the entity, so if you had CategoryAdmin we get Category.

After that we check if the Admin attribute is present, attributes have a higher priority than our guesses. If no attribute is defined or some of the values that are mandatory are not present we still try to guess.

First, we set the label and based on previous example it will be Category.

Then, we set the admin code which will be the service id, in our case it is the class name.

After, we try to find the Category entity in the list of namespaces you defined (by default it is just App\Entity). If the entity is not found an exception is thrown and you will probably need to use an attribute to define the entity. You can set the manager_type attribute per namespace.

By default we will take manager_type from attributes, if they are not present we will take it from the namespace definition. If you define the entity in your attribute but not the manager_type then we will take the manager type from the bundle configuration that will be available as a sonata_auto_configure.admin.manager_type parameter.

Then we try to guess a controller, same as for the entity we try to guess it in the list of namespaces but we add a suffix (as in most situations people name it CategoryController) that you can disable in configuration. If there is no controller we leave it as null and sonata will add its default controller.

And that is it. We have all the info we need for defining an admin class, if you used some of the other tag options when defining your admin class you will have to use attribute or register admin on your own with autoconfigure: false that would look like:

Attribute

AdminExtension