Open miroslav-mihaljevic-luminos opened 1 year ago
I just figured out that the current logic is the intended behavior, although it is kind of misleading, I expected to put the attribute on the field that I want to hide and not on the field that should control the hiding, so I guess the above code can be treated as a possible extra feature.
With current logic, the property that gets affected is the one used for attribute condition and not the one on which is the attribute.
The problematic code is from AttributeBasedLayoutVisibilityResolver:
My proposal is that the whole GetHiddenProperties() method gets replaced with this version: