OpenCut-app / OpenCut-app/OpenCut
Implementation Problem in the Feedback Flow
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 89.8k
- Forks
- 8.9k
- PR merge metrics
- No merged PRs in 30d
Description
WHY We are Storing the Feedback History in the Local Storage Where is the Source of Truth ?????
And what about the Data which goes to DB and user deleted it's Local Storage
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. Trace where feedback history is written to local storage and where feedback data is persisted to the database, then clarify the intended source of truth and the expected behavior when local storage is deleted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- databases, frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100