@Exclude with "groups"

[lazarljubenovic]

Why don't @Exclude and @Expose have a mirror API regarding their arguments? They seem like boolean switches. I expected I could easily exclude some settings for a particular group instead of turning everything off and then turning everything on except for one thing.

[zackarychapple]

Just ran into this. Had to exclude the whole class then add back all the properties with expose and one with the Expose with groups.

[MTschannett]

I know this approach from a few other libraries (in C#, Java...) but i never liked this approach.

In each of this library you can either expose everything or nothing and add back a few options.

I think this could be done better

[melanke]

+1

[belvederef]

Related issue #289

[Devidian]

Ran into this right now, have to exclude some properties for a special group - that is only called in a special place.
So i added "all other groups" to Expose.groups but this leads to a fail on all jest tests because the expected objects do not have all properties they should.

[lucas-labs]

Just run into this myself. There's one use-case where I need to exclude a certain property from an object when retrieving it to the client. The class is used everywhere. It would be way much easier to @Exclude({groups:['exlude-just-for-this-group']}). This way I don't have to go to every single place this class is being serialized to indicate that I want the property. I would be better to just exlude it in the only place I don't need it.

I ended up deleting the property by hand, which is bad, but it's a one liner vs houndreds of lines of code. I think that the ability to use groups with @Exlude would be a nice feature to have.