playground: clarify local vs One-linked UX
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 735
- Forks
- 10
- Avg merge
- 10h 47m
- Merged PRs (30d)
- 72
Description
play distinguishes local vs cloud-linked; v0play has One row + autosave but needs clearer unlinked vs linked state. P1. Related #817 #820.
Contributor guide
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 comparing the playground's local-versus-cloud-linked behavior with v0play's One row and autosave state, then read related issues #817 and #820 for context. Done means the UI clearly distinguishes unlinked and linked states in both playground and v0play flows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100