cyclestreets / cyclestreets/cyclescape
Heirarchic structuring for comments in threads?
Open
Nobody has claimed this yet.
requested-by-group-camden
threads
- Dominant language
- PLpgSQL
- Stars
- 34
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
I realise there are arguments against allowing 'comments on comments' (i.e. confusing spaghetti structures), but on balance I think the benefits outweigh the drawbacks.
George Coulouris
Camden Cyclists
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; begin by reviewing how comments and threads are currently represented. Before implementation, establish acceptance criteria for hierarchical comments and identify the relevant tests, since the current request does not define what done looks like.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100