RocketChat / RocketChat/Rocket.Chat

Requirements for modifying the source code

Open
#39,596 7 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

Requirements for modifying the source code

Add a string field key1 (keyword 1) in the channel table. The key1 field is not a unique key and can be repeated.
Add the following page to the project

Image

(1) The program opens the page shown in the following figure and passes a string value to keyword 1. Keyword 1 is a variable on this page. It searches for the channel with the string value of keyword 1 from the database, performs a fuzzy search, and displays it. Users can choose to enter the channel.

(2) Click the "Create Channel" button in the figure to create a channel for the current keyword 1. After clicking the "Create Channel" button, a "Create Channel for Keyword 1" window will be displayed. The window will show: Keyword 1: Keyword 1 string value, name: Enter the name in the text box. The rest of the content is the same as creating a regular channel. Create a channel and write the string value of keyword 1 into the key1 field of the database channel table.

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 channel table, the existing channel search flow, and the regular channel creation flow. Trace how the page can pass keyword 1 and how channel records are stored. Done means fuzzy search results are selectable, the create dialog preserves the keyword value, and new channels store it in key1.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
database, full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.