confusing new @latest tag for download badges
Open
service-badge
- Dominant language
- JavaScript
- Stars
- 27.2k
- Forks
- 5.6k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 46
Description
Isn't it very confusing to show `@latest` for both badges?
In our case we use normal releases for stable releases, and pre-releases for beta releases.
Showing both download count badges in vicinity is highly confusing for the user now.
Contributor guide
Research direction
No files, tests, or entry points are named. Locate the download badge implementation and its existing tests, then compare the stable-release and pre-release cases described in the issue; done means the two badges no longer present the same confusing @latest label.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100