Usage of @Groups

[cincas]

Hi everyone,

I think the usage of current @groups annotation is a little bit limited.

Like say we have a main entity A with multiple sub entities B,C,D

In order to use @groups, we have to put annotation across all entities, which is hard to maintain sometime.

I was hoping to have a feature like multi-level group policy.
such as
@groups({"foo"}) A
@groups({"foo.taz"}) B
@groups({"foo.bar", "foo.taz"}) C

Then if group is set to "foo", A, B and C will be shown.
if group is set to "foo.bar", both A and C will be shown, but not B

Will this be possible to make it?

Thanks.

[fullmoonissue]

+1

Hello everyone,

I have exactly the same context.

group_public_api
group_A | group_B | group_C | group_D
group_intern_api
group_E | group_F

In order to write : @groups({"group_public_api"}) => To apply to the four subgroups.

Nice day.

Best Regards,

[goetas]

I apologize for the late feedback, this probably is not your problem anymore, but for those who can still find similar issues, there are many different ways to achieve exclusion of some properties, each approach has advantages and drawbacks. Currently you can use:

• groups
• groups per property
• expression language
• custom exclusion policy

Just use the one that works better for you, there is no reason to do this: