Skip to content
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

[RFC] displaying latest version in search engine view result #1320

Closed
94noni opened this issue Jul 28, 2022 · 9 comments
Closed

[RFC] displaying latest version in search engine view result #1320

94noni opened this issue Jul 28, 2022 · 9 comments

Comments

@94noni
Copy link
Contributor

94noni commented Jul 28, 2022

Hi

I would like to know if it can be useful to display such info on http://packagist.org/ website

here is an example:
Capture d’écran 2022-07-28 à 14 08 27


We can imagine storing such data in the package when a new version is added to it
And index such data when indexing all data for the search engine

@Seldaek
Copy link
Member

Seldaek commented Jul 30, 2022

What's the value of knowing the last version in a listing though?

@IonBazan
Copy link
Contributor

IonBazan commented Sep 6, 2022

I think npm provides similar feature:
image
image

Not sure if it provides much value here but I think the last publish date would be helpful here to decide which package is still actively maintained without going to the details page.

@94noni
Copy link
Contributor Author

94noni commented Sep 6, 2022

@Seldaek @IonBazan thx for stopping here

What's the value of knowing the last version in a listing though?

mostly yes to know how a package evolve, some projects has little deps tho knowing a packages have new versions is good
also yes with the date, both could be good (mimic the npm page)

it was just an idea I got this summer tho wanted to write it down, if you think it is not that relevant, could be closed for now, thanks

@chr-hertel
Copy link
Contributor

I would argue that the search results should give info that helps a developer to choose if a package is worth investigating or not - the detail view will be used anyways btw.
I can see how stars and downloads help with that, but i don't think the version number is really relevant.
the only thing i can see is that it would be worth providing an info about stability of a package, like is there a stable version or not for example

@Seldaek
Copy link
Member

Seldaek commented Sep 14, 2022

I can see some value in the last release date to see if something's been "dead" for years, although in some cases I'd argue stuff is just stable and working and doesn't need work and thus it's fine. For example https://packagist.org/packages/seld/cli-prompt is almost 2y stale and before that it was almost 3y.. yet it "just works".

So even the date needs to be taken with a grain of salt, and newer isn't necessarily better.

The version is even less "comparable" between packages IMO, so why show it in a list?

Overall not so convinced that more info is more value.

@chr-hertel
Copy link
Contributor

True and more important for me while evaluation is the list and versions of dependencies, but that's definetly off scope for a list of results.

Filtering for compatibility with specific PHP versions would be interesting though

@94noni
Copy link
Contributor Author

94noni commented Sep 14, 2022

@Seldaek @chr-hertel fair enough, thx for taking time to comment

then we can consider closing? if it does not add much value for majority ppl

or you want to keep open to discus what can be added (not the latest version) but others data

@Seldaek
Copy link
Member

Seldaek commented Sep 14, 2022

Yeah I think I'd rather close then. We can always revisit later if there are more compelling arguments

@94noni
Copy link
Contributor Author

94noni commented Feb 24, 2024

PR as discussion draft opened here #1410
Feel free to comment :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants