Ability to Configure Hydrator Filters

[gsomoza]

Adds the ability to configure filters for the hydrator:

    // ...
    'doctrine-hydrator' => array(
        'Acme\\V1\\Rest\\User\\UserHydrator' => array (
            // ...
            'filters' => array(
                // a service...
                'Acme\\V1\\Rest\\Person\\PersonFilter',
                // .. or a lambda / anonymous function ...
                'optional_key' => function($field) {
                    return true; // will always exclude the field
                },
                // ... or an array
                array(
                    'filter'    => 'service' // or lambda,
                    'condition' => FilterComposite::CONDITION_AND, // default is OR
                ),
            ),
        ),
    ),

If this is interesting then I can throw a few more things in - e.g. a very easy way to exclude fields (by providing some built-in filters).

[veewee]

Thanks for contributing! Before I can merge this pull request, can you please make following adjustments:

• Remove closure support. This makes configuration unreadable and caching hard.
• Extra validation on interface: FilterInterface
• Add unit tests for the naming strategy and make sure that travis passes.
• Add configuration information to README.md

Maybe it is better to only allow one type of configuration. This makes this component easier to understand / use.

Maybe something like:

<?php
'doctrine-hydrator' => [
    'customhydrator' => [
        // .... other config
        'filters' => [
            'custom-filter-name' => [
                'condition' => 'and',
                'filter' => 'Filter\Key\In\ServiceManager'
            ],
        ],
    ],
],

So:

• Every custom filter has it's own configuration array.
• The condition parameter is optional. Default = OR
• the filter parameter is required.
• Every service is loaded / validated in the service-manager

When this feature is good to go, it is possible to create some build-in features if they are related to specific doctrine problems.

[gsomoza]

Sure, they're very reasonable changes - I'll have them ready soon.

[gsomoza]

Looks like the build was failing due to the php-cs-fixer. Would you like me to make a commit that includes all the changes from the fixer, even if they're not related to my changes?

[veewee]

I already fixed the cs errors on master and merged your commit. Thanks!

[gsomoza]

I forgot to add the details in the README. Will do that soon.

[veewee]

The configuration details are added to the README. Feel free to add extra information.

[gsomoza]

Added a bit more info.