pulsar-edit / package-backend

Pulsar Server Backend for Packages
https://api.pulsar-edit.dev
MIT License
11 stars 11 forks source link

[Feature Request] Package Filter #201

Closed zhaolinlau closed 9 months ago

zhaolinlau commented 9 months ago

Is this feature Currently Implemented in any way with the upstream API Server

Is your feature request related to a problem? Please describe. Kinda hard to know which package is recently updated, added, most downloads, most stars

Describe the solution you'd like Able to search package by filtering with recently updated, added, most downloads, most stars

Daeraxa commented 9 months ago

I think we have this one covered already on package-frontend. Just needs some attention which it hasn't seen in a while.

confused-Techie commented 9 months ago

So this feature absolutely already exists. It just isn't exposed via some nice UI anywhere at the moment.

But looking at the API Definition (Also our live public swagger instance if you are into that sort of thing)

We can see that (depending on some endpoints) we are already able to filter and organize packages:

So I feel like we have covered everything, being able to sort by nearly every value, order them how preferred, and as for the features that we made (As in they weren't implemented originally in Atom's backend) we can filter our results to only include grammars that support a specific file extension, or for the service it provides or consumes, or even for packages that support specific versions of a service.

So I think we have got this one covered. Otherwise as a request for this to be available in a nice UI on the website, then this issue is a duplicate of package-frontend#48 that's been attempted to be implemented in package-frontend#77.


So appreciate you contributing @zhaolinlau but I'll close this one out.

If you have any suggestions or ideas for this feature, I'd go ahead and comment further on either the issue or PR linked above.


I'll add if you want to use these features today, feel free to ask, or reference the API documentation, and all query parameters are supported in the frontend site already, so appending them manually into the URL will get you the results requested.

Such as: