nofusscomputing / nofusscomputing/centurion_ui

comment check boxes

Open
#10 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
0
Forks
0
Avg merge
1d 4h
Merged PRs (30d)
20

Description

When adding check boxes in comments like this

  • a check box
  • another checkbox

They cannot be marked as done by clicking on them. This would be handy and is already a feature in gitlab and github


EoF OP


Being able to interact with certain check boxes without having to edit the markdown, i.e. to mark it as complete improves the workflow.

Details

Add the ability to have markdown rendered with functional check boxes. then if the user changes the check boxes value, perform a HTTP/PATCH with the updated markdown. On returning HTTP/200, update the user interface.

Links

Tasks

  • Add functional checkbox support to rendered markdown.

Requirements

  • Ticket description renders interactive check boxes
  • On editing a ticket description check box, Create an action comment denoting <Marked/Unmarked> <task list description> as <Completed / Not-Completed>
  • Backend informs as part of field rendering if the check boxes are interactive

Contributor guide

Open the contributing guide

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

Start by locating the markdown rendering and field-rendering entry points, then trace the HTTP/PATCH update path and action-comment handling. The linked markdown-it-task-lists module describes the checkbox format to support. Done means rendered ticket checkboxes can be toggled, persist through HTTP/200, and produce the specified action comment while backend rendering identifies interactive fields.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.