New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Limit the number of visible options in fuzzy select #134
Comments
FuzzySelect uses search text to filter items. You shouldn't need pagination. |
well, fuzzy style searching is very useful for very large collections. when using FuzzySelect with many items, the CLI is pushed "up" inside the terminal and it is rather unwieldy. it'd be a fairly clean UI to be able to have paginated results / list (say 100 items match the fuzzy input after a few characters) to be able to navigate larger lists in addition to searching for them. |
Hey @pksunkara 🖖 I want to clarify what I'm seeing visually when using FuzzySelect with a large collection of items. Maybe there is another fix better than pagination. the top prompt is pushed off screen becomes visible again when < # lines of screen Is there a way to ensure that the list is "top aligned" so that the prompt is always visible? |
Let me paste what I said in #143.
So, in the above scenario, fuzzy select should never display all options. It should display only I will edit this issue title to represent that instead of talking about paging. |
Why is this? |
Because that is what fuzzy searching means? It's kind of like an autocomplete. Where the suggestions show up to fill the place instead of just showing all the options available. Please correct me if I am mistaken. |
i thought the use case described above was reasonably compelling. namely that at an intermediate search stage, when filtering has been applied, but there are still a large number of entries, being able to scroll through the list could be preferable to having to continue to extend the search term. For example, you might search a prefix representing a collection of objects without necessarily knowing the members of that set. But i'm speculating. I don't have a particular use-case in mind. Do you lose any other functionality by enabling paging for the fuzzy search? is there a cost associated with this? |
I don't mind implementing paging in fuzzy_select but I don't see how it is possible without overcomplicating the keypress semantics in the lib. If you look at If you look at |
That makes sense. |
it would be great to have some sort of pagination when using
FuzzySelect
with many (100-1000s) of itemsThe text was updated successfully, but these errors were encountered: