Overriding groups of deeper branches of the graph

[inwaar]

The documentation is not clear.
What do mean manager and friends array keys passed to setGroups in array?
Are those names of the properties on the object to be serialized?

Is this feature is working at all?
#1058

This seemed to remove part or all of it?

[goetas]

Hi, the feature is part of jms/serializer v3.x as described. The PR is #1071

manager and friends are the names of properties of the User class available few lines before.

The main aim of the feature is to be able to set a generic group for the whole class, and a specific group for a particular property.

As example:

use JMS\Serializer\Annotation\Groups;

class User
{
    /** @Groups({"generic"}) */
    private $name;

    /** @Groups({"specific"}) */
    private $email;

    /** 
    * @var User 
    * @Groups({"generic"})
    * */
    private $manager;
}

$context = SerializationContext::create()->setGroups(array(
    'generic',
    'manager' => array(
        'specific', 
    ),
));

will produce something as

{
  "name": "John",
  "manager": {
     "email": "[email protected]"
  }
}

If you had only

$context = SerializationContext::create()->setGroups(array(
    'generic'
));

Result would have been:

{
  "name": "John",
  "manager": {
     "name": "Tom"
  }
}

[graanday]

Hi,
is it possible to set a specific group to each friend?
specific1 for 'John friend 1'
specific2 for 'John friend 2'

[scyzoryck]

@graanday do you mean different groups depending on the object value?

[graanday]

@graanday do you mean different groups depending on the object value?

yes

I am referring to the example of the object graph in the documentation.
$john = new User( 'John', new User( 'John Manager', new User('The boss'), array( new User('John Manager friend 1'), ) ), array( new User( 'John friend 1', new User('John friend 1 manager') ), new User( 'John friend 2', new User('John friend 2 manager') ), ) );

[scyzoryck]

I guess you'd like to use it for the exclusion, right?
Then you can use ExpressionLanguageExclusionStrategy or implement your own Strategy ;-)