onecrayon / onecrayon/api.ashes.live
Request: Sort published decks by "most cloned"
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 7
- Avg merge
- 7h 39m
- Merged PRs (30d)
- 1
Description
E.g. something like:
SELECT COUNT(*), source_id, MAX(title) FROM deck WHERE source_id IN (
SELECT id FROM deck WHERE is_public IS TRUE and is_preconstructed IS FALSE
) GROUP BY source_id ORDER BY COUNT(*) DESC;
Gives a peek at what decks people are copying.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The issue provides a SQL example for counting cloned decks and ordering them by clone count, but it names no files, tests, or API entry point. Start by locating the endpoint that lists published decks and its database query. Done means published, non-preconstructed decks can be returned in most-cloned order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, sql
- Domain
- api, backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100