Support rendering of client behaviors inside simple composite components
- Dominant language
- Java
- Stars
- 127
- Forks
- 59
- Avg merge
- 23h
- Merged PRs (30d)
- 7
Description
It is already possible to attach behaviors to composite components that are retargeted to via but is not possible to attach a behavior directly to a composite component, with no target).
UINamingContainer should implement ClientBehaviorHolder and support decoding of behaviors. It should be possible to configure the supported events using the with no "name" attribute or maybe with the special keyword "@this" in the "targets" attribute.
The script of a behavior could be made available in the composite component implementation for example via an EL expression.
Example usage:
...
#### Affected Versions
[2.2]
Contributor guide
Research direction
Start by reviewing UINamingContainer and the existing composite-component behavior handling described through cc:clientBehavior. Clarify how direct behaviors should be configured and how their scripts should be exposed to the composite implementation. Done means direct behaviors can be declared without a target, decoded, and made available for rendering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100