onecrayon / onecrayon/api.ashes.live
Feature: Events
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 7
- Avg merge
- 7h 39m
- Merged PRs (30d)
- 1
Description
Had a request for the ability to create events and associate decks with them. Some thoughts:
- Allow submitting private snapshots, with the understanding that they will be automatically switched to public snapshots when the event is complete? I worry about requiring decks to be public to submit, because then the person who submits last can make a very educated guess about what they're likely to see in others' decks and tech for it (so all decks should be made public at once, even if the deck lists are public for the event)
- Show statistics about card/dice usage on the event page, along with a deck listing of decks that were used
- Two modes? Looking for entrants (submit private snapshots) vs. event complete (snapshots moved to public)?
- Link to event from the deck details sidebar?
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 names no files, tests, or entry points. Begin by mapping the existing deck and snapshot API behavior, then clarify the event lifecycle, privacy transition, statistics, deck listing, and deck-detail link before implementation; done should cover an agreed event workflow and its tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100