NickFitton / NickFitton/FortSprite
Decide friend collection-view presentation and availability semantics
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
Define the precise read-only collection experience after friendship: how the owner is identified, what the matrix and summary show, how live updates and loading/failure states behave, and what happens when access is revoked while the view is open. Keep anonymous progress excluded.
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 parent issue #16 and the questions in this issue. Define the read-only collection-view semantics for owner identification, the matrix and summary, live updates, loading and failure states, revocation during viewing, and exclusion of anonymous progress. Done means these behaviors are precise enough to guide implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100