RocketChat / RocketChat/Rocket.Chat

Additional alias names of custom emojis not accepted anymore

Open
#18,264 36 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description:

According to our docs, it should be possible to add multiple alias names to custom emojis, separated by space character:

Enter a name for your emoji, add space separated list of the aliases for the emoji which can be entered to display the emoji in the chats

This does not seem to be working anymore, the space character will be replaced by a dash instead.

Steps to reproduce:
  1. Add a new custom emoji
  2. Give it multiple aliases, e.g. first second
  3. Hit save, see how the alias gets transformed into: first_second
Expected behavior:

It should separate the alias input by space, as stated in the docs, and accept multiple alias names.

Actual behavior:

Space character gets replaced by dash. Multiple aliases not possible.

Server Setup Information:
  • Version of Rocket.Chat Server: 3.4.0
  • Operating System: Linux
  • Deployment Method: Docker
  • Number of Running Instances: Docker
  • DB Replicaset Oplog: Yes
  • NodeJS Version: Docker
  • MongoDB Version: Docker
Additional context
Demo video

Bildschirmfoto 2020-07-15 um 10 45 26

Task: DOCS-1320

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 reproducing the custom emoji creation flow with the documented aliases first second, then trace where the alias input is transformed during save. Compare the saved result with the expected separate aliases and verify that multiple aliases can be entered and used in chat.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
content, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.