Description
Keep our programming model with mixins as it is (contract by constructor), but don't strictly require mixins to actually store the holder that they are associated with. We only require this now, because of implementation details of the framework.
Currently we do a reflective field search in the mixins to get hold of the holder instance which is not guaranteed to work due to potential ambiguity.
Attachments
Issue Links
- breaks
-
CAUSEWAY-2540 Regression: bulk select from mixin actions is broken
- Closed