sillsdev / sillsdev/languageforge-lexbox

Commenting support

Open
#1,765 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

💻 FW Lite 📖 MiniLcm Epic Needs design
Dominant language
C#
Stars
9
Forks
8
Avg merge
2d 13h
Merged PRs (30d)
49

Description

Describe the feature

Features:

  • comment threads, allowing someone to reply to a specific comment
  • mention a field in the entry (nice to have)
  • reference another entry which is rendered as a link in the comment (nice to have)
  • comment authors
  • comment only permission
  • resolving comments
  • comment reactions?
  • comment activity, per device CommentId tracks read status, local only.
  • Permissions, edit delete your own, managers can delete any comment or thread. Comment only has the same permissions as editor.
  • Limit text to 2k chars, reject empty comments.
  • import LF comments (nice to have)

UI:

  • On each entry/sense/example comments can be made and seen as threads which have to be explicitly opened, this is to help handle read status.
  • There should be a sort of activity view to find unread comments or threads. By default it should sort by comment date and filter to only unread comments. There should be a button to mark all as read. It would be nice to have a toggle to change the sort order by sync date, and show all comments. MVP UI can just list comments, we can expand it to list per thread or per subject later. There should be a way to jump to the entry/subject that the comment was made on.
  • If a comment was edited (eg CreateDate != UpdatedDate) then highlight that in the UI.
  • Show a comment history button if edited.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Before implementation, split the requested comment, permission, activity, and UI behaviors into an agreed MVP with acceptance criteria; done should be defined before work starts.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
authorization, full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.