It should avoid conflicts in expose rules

[slavafomin]

I've added a broken test to demonstrate another issue with conflicting expose rules. Here, I'm using set of expose rules to control object transformation from plain to class and another from class to plain. For some reason there is a conflict. Password should not be set for "update" group, but it is.

[cojack]

@slavafomin how it should works if @Expose decorator bind meta by key name, so basically it overrides one by one.

[slavafomin]

Hello @cojack, this was a long time ago, I can't tell exactly what the issues was about.

I think the idea was that expose decorators shouldn't be mutually exclusive, but rather they should build a list of rules, which are followed in the [de]serialization process, because as a developers we want more granular control based on the different serialization groups and serialization direction (from-plain/to-plain).

In order to solve this the rules should be stored as a list for each object property rather than a single rule for each property.

[NoNameProvided]

Closing in favor of #378 to allow refactor.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.