Unless I am wrong, when an ApiResource field can be serialized within different context, the context is ignored - so the second time a schema is generated, the previous definition is taken into account.
For instance, in
/**
...
@Groups({"g1", "g2"})
*/
public $myfield;
The schema definition will be corrected for the first serialization group used, but not for the second.
Unless I am wrong, when an
ApiResourcefield can be serialized within different context, the context is ignored - so the second time a schema is generated, the previous definition is taken into account.For instance, in
The schema definition will be corrected for the first serialization group used, but not for the second.