-
-
Notifications
You must be signed in to change notification settings - Fork 474
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
Sorting of search results #365
Comments
That's already the case to some extent (packagist favs & downloads in the last month are taken into account). The rest isn't possible because nobody did it yet. |
I'm really not under the impression it sorts by favorites or downloads. Really when I type something it pretty much just returns results in an order that seem random at best or at least not helpful. I think in the long term Packagist should just deprecate the built-in favorite system to use Github and Bitbucket's stars/followers count which is displayed in the API. I don't think enough people use the favorites on Packagist for it to be a trusted sorting index. I did that in my Laravel packages registry that wraps around the Packagist API and it yields much better results than what you'd get by typing "laravel" on Packagist I think. Any improvement to the sorting algorithm would be welcome in my opinion, really. |
Completely agree on this issue. I would love to sort by stars and downloads, and even better would be to pull in stars from Github. |
+1 |
Some tags are now way too deep to find anything..... +1 |
+1 |
Is there any workaround for this? E.g. any alternative UIs on the web that use the Packagist API to provide basic functionality? Currently the UI is next to useless to browse for unknown packages, e.g.
has 27 pages of results, in no discernible order. |
+1 |
1 similar comment
+1 |
+1 this really should be a feature |
+1. @Seldaek , can I ask you for a little subset of a database again so I can do a PR? The last I have comes from veeeeeery old times. |
Solr is used for search on composer, so in addition to sorting some facets would be good too... |
+1 and probably consider switching to elasticsearch, Solr is terrible for this sort of thing... |
Yes please 👍 |
Total in favor of this 👍 ! The search results do not seem to have a noticeable pattern. Let me give an example of how the current search results are pretty hard to navigate through. I was looking for a mailer library. The most popular result on the first result page had about 7000 downloads and 4 favorites. Then I navigated to page two and found Swiftmailer. This library had 5million+ downloads and 40+ favorites. On that first result page there was even a library that was marked as "abandoned". As a result I ended up navigating through all 9 pages to see if there were any other popular libraries that happened to be stuck at the end. I suggest making this a tabular result set. Allowing ordering by column. I also suggest adding a updated_at column which would be extremely useful to find out how stale a library may be. |
As it stands, you can only find a package if:
It'd be nice not to have to incur the technical debt from the latter. |
+1 if you need some hands to help also |
+1 |
5 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
i have my brutal solution for this.
Please don't use this when phrase is not precise and packagist return 100 pages of results --------- Edit: |
+1 |
I created a gist with a (temporary) solution for CLI, which I'm using. Maybe someone could find it useful. |
+1 |
You can now sort by Stars and Downloads |
@Seldaek OMG THIS IS THE GREATEST WOOOOOOO |
Cool ;-) |
THANK YOU SO MUCH! |
Great :) |
So much yes |
great, and thanks to remove my solution ;) indeed it's not useful anymore. |
hmm ...?? I would like to sort by
|
How do you sort by downloads / stars? It's not very obvious |
I think the feature used to be there (sorting) but it is gone now #818 ? |
In order to get better package selection, it would be good to sort results based on downloads, number of stars, forks, any other things that promote package maturity.
The text was updated successfully, but these errors were encountered: