Hi,
Can we make aggregations sorting more flexible, to prevent the selected items from going to the top of the list
here an example :
when I select 2022, it go to the top of the list, in my case it should stay at it initial position (ordered by terms)
It make some confusion for users when selecting many items :
the affected code is in the helper.js file :
if (sort === 'term') {
buckets = .orderBy(buckets, ['selected', 'key'], ['desc', order || 'asc']);
} else {
buckets = .orderBy(buckets, ['selected', 'doc_count', 'key'], ['desc', order || 'desc', 'asc']);
}
the 'selected' key is hard coded in this file, it should be more flexible so we can order with custom criteria , or simply remove the 'selected' param if not needed.
Hi, Can we make aggregations sorting more flexible, to prevent the selected items from going to the top of the list
here an example :
when I select 2022, it go to the top of the list, in my case it should stay at it initial position (ordered by terms)
It make some confusion for users when selecting many items : the affected code is in the helper.js file :
the 'selected' key is hard coded in this file, it should be more flexible so we can order with custom criteria , or simply remove the 'selected' param if not needed.
Thanks