Prevent Duplicate Tastings
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 103
- Forks
- 18
- Avg merge
- 1h 19m
- Merged PRs (30d)
- 555
Description
Due to network issues (or UI jank) its possible to often submit a duplicate tasting record without even knowing it. This is pretty easily preventable on our end so lets implement it in the API layer. Probably something like an hour timeout? Maybe a day? It also helps avoid abuse.
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
Start by locating the API entry point that creates tasting records and read how submissions are currently handled. Clarify the intended duplicate-detection window, then verify the API behavior for repeated submissions and abuse-related cases. Done means duplicate tasting records are prevented according to the agreed window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100