Backport MEME Comment

[benloh]

This does two main things:

1. Parity with MEME Comment system

• ac-comment and dc-comment should be basically equivalant
• URComment* components should be basically equivalent with the conversion of UNISYS calls
• URCommentThreadMgr has been replaced by URCommentCollectionMgr and all buttons are now managed via URCommentStatus
• comment-mgr should have a similar API, with mostly database calls unique to each system.

2. NCNodeTable and NCEdgeTable have been refactored to be simpler functional components.

Wiki Update

(To be added to wiki with the PR)

Comment Templates

Defining Comment Types in the Project Template file

Comment types can be defined in the project's *.template.toml file.

[[commentTypes]]
slug = "cmt"
label = "Comment"

  [[commentTypes.prompts]]
  format = "text"
  prompt = "My Comment"
  help = "You might start with 'I think...'"
  feedback = "Feedback is displayed below the input field."

[[commentTypes]]
slug = "evidence"
label = "Evidence Critique or Suggestion"

  [[commentTypes.prompts]]
  format = "dropdown"
  prompt = "Is this supported by evidence?"
  options = ['😀 Yes', '🤔 Some', '🥲 No']
  help = "Select one."
  feedback = "Only one is selectable"
   
  [[commentTypes.prompts]]
  format = "text"
  prompt = "What would you change?"
  help = "Please be specific to help your friend."

Cascading Comment Types

1. By default, the first comment type defined in *.template.toml is used as the default comment type.
2. Any new project will use the comment types defined in _default.template.toml. You can edit that file to have new projects automatically use the comment types defined in _default.template.toml.
3. If there is no type defined in the *.template.toml file, the system will first try to use the types defined DEFAULT_CommentTypes in dc-comments. This allows you to assign a standard set of comments if you're comfortable code diving, but is not intended for regular use.
4. If DEFAULT_CommentTypes is not defined in dc-comments, the system will fall back to a single generic template. This ensures that there is ALWAYS a usable comment type even if the project and dc-comments are not defined:

const DEFAULT_COMMENTTYPE: TCommentType = {
  slug: 'cmt',
  label: 'Comment', // comment type label
  prompts: [
    {
      format: 'text',
      prompt: 'Comment', // prompt label
      help: 'Use this for any general comment.',
      feedback: ''
    }
  ]
};

Valid Slugs

Currently (as of 1/6/2025), known CType slugs are:

export type CType =
  | 'cmt'
  | 'tellmemore'
  | 'source'
  | 'evidence'
  | 'clarity'
  | 'steps'
  | 'response'
  | string;

...but you can also use any other string for a custom comment.

NOTES

• As of 1/6/2025 there is currently no WYSWIG editor for template.toml. You need to edit these by hand.

[benloh]

@jdanish Please QA the comment system. The MEME comment system should work like NC's with the addition of being able to set comment types via the project template file.

[jdanish]

OK! Do you want me to post issues or comments here if I find things? Also, are the notifications part of the update? I noticed an error there earlier ... Thanks!

[jdanish]

Specifically, clicking on the comment number generates an error...

[benloh]

Thanks! A new issue would be helpful for tracking. Otherwise we end up with a hodge podge of comments and replies.

[jdanish]

OK, added #321

Will you see these if assigned or do they need to be in project too?