appbaseio/reactivesearch

Consider show count numbers for SingleRange

Open

#836 ouverte le 18 févr. 2019

Voir sur GitHub
 (1 commentaire) (1 réaction) (0 assignés)JavaScript (4 835 stars) (487 forks)batch import
enhancementhelp wanted

Description

Issue Type: enhancement

Platform: web

Description:

I'm a searchkit user, I'm tring to migrate my searchkit project into reactivesearch. reactivesearch is much faster than searchkit!

However, the SingleRange has no count number is not same as searchkit, I think show the aggs of each range, will be a necessary feature (at least its very useful for me and my users), since SingleList could able to show count, but SingleRange couldn't is a little bit weird.

I found here had a similar closed issue #269, a boolean option such as showCount will be great, but it still not work in v3.0 now.

Hope this feature could be considered

Best regards

Guide contributeur

Stack technique
javascriptreact
Domaine
frontend
Type d'issue
feature
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
1-3 hours
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
stale
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
clear
Prérequis
Familiarity with reactivesearch componentsUnderstanding of search aggregations
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
70
Direction de recherche
To implement showCount for SingleRange, first examine the existing SingleList component to understand how it renders count numbers and uses the showCount prop. Then locate the SingleRange component (likely in packages/web/src/components/range/ or similar). The logic should fetch aggregations for each range and display the count. Review the closed issue #269 for additional context. Ensure that the prop is added to the component's API and documented appropriately.