Download the PHP package mark-gerarts/automapper-plus-bundle without Composer

AutoMapperPlusBundle

A Symfony bundle for AutoMapper+. To see it in action, check out the demo app.

Table of Contents

• Installation
• Usage
• Configuration
• Further reading

Installation

The bundle is available on packagist:

Don't forget to register the bundle:

Usage

The automapper is available as a service: automapper_plus.mapper (or just type hint the AutoMapperPlus\AutoMapperInterface).

You can register mapping configurations by creating a class that implements the AutoMapperConfiguratorInterface. This configurator class will have to define a configure method, that gets passed the configuration object:

If you use autowiring, the configurators will be picked up automatically. Alternatively, you'll have to register the class as a service and tag it with automapper_plus.configurator. You can optionally add a priority parameter to the tag.

You can register all your mappings in a single configurator class, or spread it across multiple classes. The choice is yours!

Configuration

The options for the mapper can be configured. Create a config/packages/automapper_plus.yaml file (or add to your config.yaml for older Symfony versions) with the following contents:

These options correspond with the ones of the Options object.

Full reference (Not all options are supported at the moment, more coming soon!):

Using the configuration is completely optional, you can just set the options directly on the Options object in one of your configurators using $config->getOptions().

Symfony property accessors

The bundle contains a bridge for the Symfony PropertyAccessor. It provides 2 variants:

• The SymfonyPropertyAccessorBridge is basically only the functionality of Symfony's component, meaning you can NOT set private properties directly (which is a good thing if you want to be more strict).
• The DecoratedPropertyAccessor uses the Symfony property access, but falls back to the default in case of failure. This means private properties will be handled, even if they don't have a getter/setter.

Both options provide allow to use fromProperty with full property paths, e.g. forMember('aProperty', Operation::fromProperty('some.nested[child]'));. Note that other usages of property paths have not been tested and are not guaranteed to work. It will be investigated in the 2.x release (related issue).

Sample service definition:

In your automapper_plus.yaml configuration:

Further reading

For more info regarding the automapper itself, check out the project page.