MoeraOrg / MoeraOrg/moera-issues
Posting/comment attributes
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 20
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Make possible to set to every posting/comment a JSON object with arbitrary attributes. In distinction from posting/comment body, the attributes object is not versioned and not signed. When a posting is picked from another node, its attributes are also copied.
The current fields acceptedReactions*, reactions*Visible may be moved into the attributes object. Also attributes for switching comments on/off and notification settings may be added.
Attributes known by node may have their type and value validated.
Node should impose limits on the size of the attributes. Also attributes should be stored in a separate table to be able to store identical attributes only once to conserve DB space. Use unique HASH index for it.
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
No implementation files or tests are named. Start by locating how posting/comment persistence and the current acceptedReactions fields are handled; done would cover attribute copying, validation, size limits, and deduplicated separate-table storage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100