Affects Version/s: None
Security Level: Public (Public: Anyone can view)
KULRICE-4718 Generalize data dictionary section structure and introduce Group concept KULRICE-7488 Uif-DropdownControl style not propagated to <select> element KULRICE-5437 UIF Framework - Add standard markup for table semantics KULRICE-8899 Introduce LocalCurrency and LocalDecimal data types KULRICE-9118 Implement better support for a concept similar to ExternalizableBusinessObjects in the new krad-data framework KULRICE-5366 Uif Framework - Collections: Support for duplicate key check in collections and highlighting attributes KULRICE-11301 UIF-related annotations should not be in krad data module KULRICE-5282 Uif Framework - Binding needs to look at forceUppercase KULRICE-828 Unify the Node Settings concept into the Configuration framework KULRICE-8939 Move non-UIF dependent components out of KRAD app-framework module
KAI Review Status:Not Required
KTI Review Status:Not Required
In order to better support some of the upcoming features we need the facility to add additional HTML custom attributes (part of the HMTL5) spec. Here is a rough outline:
I think this would be a good time to introduce the concept for future work (we can decide if we want to rewrite existing code later).
Should be easy to implement:
- Add Map<String, String> data to ComponentBase (and Component interface)
- In attributeBuilding.tag, build up a new data variable. This would read the map entries and for each entry add the attribute with 'data-
"' to the variable string.
- Pick up the new variables from span, div tag builders and other templates after call to attributeBuilder
Then in the script tag pass the component and call attributeBuilder, then adding the data variable would result in:
<input type="hidden" data-role="script" data-for="u99"/>
Then when doing refresh on the component we can find its script with:
jq('hidden[data-role="script"][data-for="' + componentId + '"])