RocketChat / RocketChat/Rocket.Chat

dynamic slug for stared message not working

Open
#31,727 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description:

If we want to search through the star message , the ?msg= is updating in a wrong way

Steps to reproduce:
  1. Go to menu in top-right corner
  2. Click it and select star messaged
  3. On browsing thorugh message you can clearly see the error.

###current behavior:

https://github.com/RocketChat/Rocket.Chat/assets/93787385/5e2948ac-67c1-4696-86ac-3bb1338619c5

Server Setup Information:
  • Version of Rocket.Chat Server: 6.4.8
  • Operating System: win 10
  • Deployment Method: docker
  • Number of Running Instances: 1
  • DB Replicaset Oplog: enabled
  • NodeJS Version: 14.x
  • MongoDB Version: 6.x
Client Setup Information
  • Desktop App or Browser Version: browser
  • Operating System: win 10
Additional context

This is exaclty similiar to issue https://github.com/RocketChat/Rocket.Chat/issues/31653

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 starred-message navigation in a browser and inspect how the ?msg= URL changes while browsing messages. Compare the behavior with issue #31653; done means the query parameter updates to the correct message and remains usable throughout navigation.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.