RocketChat / RocketChat/Rocket.Chat
roles.addUserToRole - Error: API endpoint does not exist
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:
The API endpoint roles.addUserToRole does not exist.
When called it responds 400 - Bad Request as well.
Steps to reproduce:
- Go to the endpoint in your browser or curl the endpoint
Expected behavior:
The endpoint to function
Actual behavior:
The endpoint does not function, it sends a 400 Bad Request in curl and says endpoint does not exist when accessed from a browser.
Server Setup Information:
- Version of Rocket.Chat Server: 3.12.1
- Operating System: Ubuntu 20.04
- Deployment Method: snap
- Number of Running Instances: 1
- DB Replicaset Oplog: Enabled
- NodeJS Version: 12.18.4
- MongoDB Version: 3.6.14
Client Setup Information
- Desktop App or Browser Version: Browser - Chrome
- Operating System: Windows 10
Additional context
Relevant logs:
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 locating the API registration or entry point for roles.addUserToRole and reproduce the request described in the issue against Rocket.Chat 3.12.1. Determine why it returns 400 or reports that the endpoint does not exist; done means the endpoint responds according to its intended behavior and the regression is covered by an appropriate test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100