RocketChat / RocketChat/Rocket.Chat
Rename a room and return to the old name
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Rename a room and return to the old name doesn't work: error-duplicate-handle.
Steps to reproduce:
- Create the room "test".
- Rename it to "test1".
- Rename it to "test".
Expected behavior:
The room get renamed.
Actual behavior:
The room didn't get renamed.
Server Setup Information:
- Version of Rocket.Chat Server: 3.13.2
- Operating System: Ubuntu
- Deployment Method: Docker
- Number of Running Instances: 2
- DB Replicaset Oplog: Yes
- NodeJS Version: v12.21.0
- MongoDB Version: 4.0.23
Client Setup Information
- Desktop App or Browser Version: Firefox 87
- Operating System: Win 10
Additional context
No.
Relevant logs:
No log entry.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the room rename sequence described in the issue on the reported Rocket.Chat server setup, then trace the room rename entry point and duplicate-handle validation. Done means a room can be renamed from its original name to another name and back without error-duplicate-handle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100