NickFitton / NickFitton/FortSprite
Decide request and friendship lifecycle invariants
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Part of #16
Question
Specify the social-record contract that correctly represents outgoing and incoming requests, acceptance, decline, removal, re-requesting, self-links, duplicate sends, crossed requests, and stale actions. The result must give every operation an unambiguous authorization and idempotency rule.
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 reading the parent issue #16 and this issue's listed lifecycle cases. Define the contract for outgoing and incoming requests, acceptance, decline, removal, re-requesting, self-links, duplicates, crossed requests, and stale actions. Done means every operation has an explicit authorization and idempotency rule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authorization, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100