You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only children of type UIColumn should be processed by renderers associated with this component.
But why stop there? When what makes this component quite powerful is the "saving state per row algorithm"... It's gonna be a repeat of #1837, but in PrimeFaces we had to create a custom UIData to support other kind of children (like p:columns). Also, UIRepeat seem very similar to UIData and yet are two different component
IMO, the spec should "allow" UIData to have more children than just UIColumn so they can be processed. Also, it should handle cases where children is also UIData (that would solve this problem #1837 I think).
As a quick example what it could look like in UIData:
Where UIData#isEligibleChildren() returns whether or not children should be visited/processed etc. (where this method is protected and can be overrided)
WDYT?
The text was updated successfully, but these errors were encountered:
According to the spec:
But why stop there? When what makes this component quite powerful is the "saving state per row algorithm"... It's gonna be a repeat of #1837, but in PrimeFaces we had to create a custom UIData to support other kind of children (like p:columns). Also, UIRepeat seem very similar to UIData and yet are two different component
IMO, the spec should "allow" UIData to have more children than just UIColumn so they can be processed. Also, it should handle cases where children is also UIData (that would solve this problem #1837 I think).
As a quick example what it could look like in
UIData
:Where
UIData#isEligibleChildren()
returns whether or not children should be visited/processed etc. (where this method is protected and can be overrided)WDYT?
The text was updated successfully, but these errors were encountered: