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
By far the most popular and useful way to use a numberDisplay is with a groupAll object. The usage is
numberDisplay.group(cf.groupAll())// just count all records (for example.valueAccessor(x=>x)// do not try to fetch .value since groupAll.value() returns a value
But apparently it was originally designed to work with ordinary groups, so it also looks for group.all(), sorts that, takes the first one, and extracts its .value.
It's not as simple and straighforward as the renames in the dataTable, dataGrid#855, and dataCount#1499, but we could split this method into .group() and .groupAll(), warn if you use one when you meant the other, or even err out if you give a group to groupAll, and default the valueAccessor to identity (as shown above) if groupAll is used.
The text was updated successfully, but these errors were encountered:
By far the most popular and useful way to use a numberDisplay is with a groupAll object. The usage is
But apparently it was originally designed to work with ordinary groups, so it also looks for
group.all()
, sorts that, takes the first one, and extracts its.value
.It's not as simple and straighforward as the renames in the
dataTable
,dataGrid
#855, anddataCount
#1499, but we could split this method into.group()
and.groupAll()
, warn if you use one when you meant the other, or even err out if you give a group to groupAll, and default the valueAccessor to identity (as shown above) if groupAll is used.The text was updated successfully, but these errors were encountered: