Download a leaderboard as CSV
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 90/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- data-visualization, frontend
Research direction
In web/template.html, read renderBoard() and ranked(scope, cat) to see how the filtered leaderboard rows are built. Start with npm run data, then npm run build and open site/leaderboard.html. Add the browser download using a Blob and an a download element; confirm the CSV includes all filtered rows and opens cleanly in Excel or Google Sheets with names containing commas and quotes.
Written by the indexing model from the issue text.
Description
People will want the numbers in a spreadsheet.
What to build
- A "Download CSV" button next to the leaderboard's search box that downloads the list as it is filtered (place and category), with columns: rank, login, location, name, state, parish, and every category.
- Built in the browser (a
Bloband an<a download>), no server.
Where
- web/template.html:
renderBoard()builds the list;ranked(scope, cat)gives every row, not only the first 100.
Done when
- The file opens cleanly in Excel and Google Sheets, including names with commas and quotes.
Getting started: npm run data, then npm run build, then open site/leaderboard.html. No dependencies; see CONTRIBUTING.md.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from wbp318/github-leaderboard
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement help wanted
Difficulty 5/5 Over a week Newbie friendliness 45/100
wbp318/github-leaderboard#10 ·
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 54/100
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
accessibility help wanted
Difficulty 3/5 1-2 days Newbie friendliness 78/100
All issues in wbp318/github-leaderboard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
good first issue tests
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
eliasstravik/herdr-projects#1032 ·
-
1️⃣ phase/under-investigation flaky/confirmed flaky/needs-decision type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
growilabs/growi#12246 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
TMHSDigital/Free-Game-Dev-Assets#301 ·
Maintainers usually reply within 1 day