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
In regards to when or when not to utilize the filterValue attribute...I was under the impression that the attribute was to be used if a filter was not explicitly defined in a filter facet via <f:facet name="filter">. Or in other words, the filterValue attribute was to be ignored if I did define a filter facet.
As there are two potential ways to define default value, users are confused which one to used, but more recently users tend to use custom facet filter value due to a "regression"
So, maybe the best way to go about it is to support both by simply doing a coalesce 😄 I can propose a fix, but maybe in another issue, your issue is pretty clear as to what is not working /confusing
Describe the solution you would like
support both UIColumn#filterValue and custom facet value, UIColumn#filterValue being priority number 1
Additional context
No response
The text was updated successfully, but these errors were encountered:
Description
Based on this: #9349 (comment)
As there are two potential ways to define default value, users are confused which one to used, but more recently users tend to use custom facet filter value due to a "regression"
My solution is here #9349 (comment)
Describe the solution you would like
support both
UIColumn#filterValue
and custom facet value,UIColumn#filterValue
being priority number 1Additional context
No response
The text was updated successfully, but these errors were encountered: