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
The use of reverse: boolean in ChannelDomainOptions is confusing because it doesn’t mean (exactly) to reverse the order: it means to use descending natural order instead of ascending natural order. The difference is that descending natural order still puts null/unorderable values last, whereas reversing ascending natural order would put null/unorderable values first. Therefore it would probably make more sense to add a order option to the ChannelDomainOptions interface, and change the meaning of the reverse option so that it puts nulls first (assuming that you leave order as the default ascending). We could also allow the order option in ChannelDomainOptions to be specified as a comparator function.
I was struggling to remember I needed to specify
order: "descending"
instead ofreverse: true
. Perhaps we could support both?The text was updated successfully, but these errors were encountered: