enable jms max depth exclusion strategy

[jbouzekri]

It adds a call to the ViewHandler to enable the max depth strategy exclusion in jms serializer context.

Best regards

[lsmith77]

so the actual max depth will then still need to be set on the context by the user?

[jbouzekri]

Not exactly, the user enable this jms context feature by setting in a parameters.yml file :

fos_rest.serializer.exclusion_strategy.max_depth: true

Then he can use the max_depth property in his JMS configuration. For example, in the file MyBundle/Resources/config/serializer/Item.yml :

MyBundle\Entity\Item:
    exclusion_policy: ALL
    properties:
        children:
            expose: true
            max_depth: 3

[lsmith77]

ok .. but this config should then be added to the DI extension. furthermore please also add some infos to the docs on this. finally please also add a test case.

[jbouzekri]

Yeah I wanted to see if this pull request was acceptable. For the DIC extension, my bad, I just saw that there was a serializer section. Ok I will work on it shortly.

[jbouzekri]

What an idiot I am. I just made a search on MaxDepth and I found that this feature was implemented for the View using annotation.

/**
 * @View(
 *  serializerEnableMaxDepthChecks=false
 * )
 */

After looking at what happens in the ViewResponseListener, I have created a CustomView extending the normal View and overrided the create static method and use it in my controllers (as I don't like annotation) :

use FOS\RestBundle\View\View as BaseView;

class View extends BaseView
{
    /**
     * {@inheritDoc}
     */
    public static function create($data = null, $statusCode = null, array $headers = array())
    {
        $view = parent::create($data, $statusCode, $headers);
        $view->getSerializationContext()->enableMaxDepthChecks();
        return $view;
    }
}

So i will close this pull request. Thanks for your time.