atom / atom.io

šŸŒ A place for feedback on the atom.io website and package API
158 stars 98 forks source link

Package listing on atom.io contains defunct/broken packages #71

Open Sequoia opened 8 years ago

Sequoia commented 8 years ago

Example: https://atom.io/packages/mocha-snippets

This is frustrating because you can still search in atom & find the package, only when you attempt to install do you get an issue.

Best Solution, IMO

Log 400 errors like

https://www.atom.io/api/packages/mocha-snippets/versions/0.1.0/tarball: 400 Bad Request Repository inaccessible

When a package get "repository inaccessible" over multiple days, remove it from atom.io (or remove it from search results & flag it as not working).

Easiest solution

Put a link on package pages (and search results in-application) like: "Package missing? File an issue here."

neeklamy commented 8 years ago

One thing Iā€™d add, there should always be a way to flag up any other problems.

Currently the microcopy on an individual package page reads:

Flag as spam or malicious

Just change that to something general:

Something wrong wth this package?

Following that link then opens a pop-up window, that too should be generalised, currently itā€™s:

I think this package is bad news.

How about this?

I think thereā€™s something wrong.

Suggestion for improved wording on package flagging screen.
jclaveau commented 5 years ago

This is super deceptive especially when you discover Atom and dig in packages repository to fit your needs.

Example https://atom.io/packages/atom-project