RocketChat / RocketChat/Rocket.Chat

FEAT: Add ordered and unordered list formatting with auto-continuation in Rocket Chat message composer

Open
#38,862 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: feature
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description

Add ordered and unordered list formatting tools to the message composer, similar to modern text editors like Notion and Slack. This will improve user experience by eliminating the need to manually type list markers.

Problem

Currently, users must manually type list markers (1., 2., -, etc.) when creating lists in messages. This is tedious and breaks the flow of writing, especially for longer lists.

User Experience Benefits

  • Faster list creation
  • Consistent formatting across all messages
  • Familiar behavior matching Notion, Slack, Discord
  • Reduced cognitive load (no manual numbering)

Proof of concept

https://github.com/user-attachments/assets/c529fe17-e4d7-45d5-ad3f-7f64d4cabfac

Note-

This aligns with industry standards and will significantly improve the writing experience for users creating structured content in messages.
I would like to implement this feature by contributing a PR that resolves this implementation. I'd appreciate feedback from the Rocket.Chat team on this feature proposal and the suggested implementation approach before I begin work.

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 Rocket.Chat’s message composer implementation and review the linked proof of concept for the intended behavior. Define the scope for ordered and unordered list formatting, including auto-continuation, and consider the issue complete when both list types work consistently in message composition.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.