Add persistence feature
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 204
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
I'd like to be able to shut down the server and then re-open it against the same commit range and have the comments still there. Perhaps not the default, but a flag you could use. Obviously a fairly substantial overhaul. Closely related to #28.
Perhaps even just some kind of LRU browser local storage, keyed off the commit range in question.
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 issue #28 and comparing the server shutdown/reopen workflow with the proposed browser local-storage alternative. Define how comments are keyed to a commit range and whether persistence is enabled by a flag; done means comments remain available after reopening the same range.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100