-
Notifications
You must be signed in to change notification settings - Fork 47
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
Optionally restrict searches to package or function results #290
Comments
What about three sections with links at the top to the top of each section? |
I think that might pose an issue if we have an upper bound on the number of results (which, if I remember correctly, we do)? |
Well we could impose a limit in each category separately. |
Ok, true. I think both would work, yeah. I guess it would be better to separate function and package results. |
Actually on second thoughts I think my original suggestion is best, as I think it makes the most sense to interleave different types of results by default according to relevance. Having separate sections could mean that the first few results you see are only very tenuously related to the query — imagine a case where the section which is displayed first has lots of low-relevance results, and the section displayed after that has lots of high-relevance results. |
Suggestion from @marick. I'm imagining 3 radio buttons just above the list of search results:
This, together with #147, should make it much easier to find packages for a particular task if you aren't already familiar with the ecosystem.
The text was updated successfully, but these errors were encountered: