RocketChat / RocketChat/Rocket.Chat
Wrong username warning or error not showed
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:
- Whilst creating new account on rc if the user provide wrong usename
- no error message or warning is being given
- Even account is not made but don't know what went wrong
https://github.com/RocketChat/Rocket.Chat/assets/133019575/5b62dd37-cea4-4453-863a-731400c5f901
Steps to reproduce:
- go on create new user
- provide wrong username
- no warning is given there also if you click save even than no error message is being shown
Expected behavior:
- should show warning in case wrong username
- must give error incase worng username is provided and clicked on save
Actual behavior:
- don't now what went wrong while creating account in case wrong user name is being provided
Server Setup Information:
- Version of Rocket.Chat Server: 6
- Operating System: win 10
- Deployment Method: production + wsl 2
- Number of Running Instances: 1
- DB Replicaset Oplog: true
- NodeJS Version: 14
- MongoDB Version:6
Client Setup Information
- Desktop App or Browser Version: production
- Operating System: win 10
Additional context
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 issue in the create-new-user flow using the reported steps: enter an invalid username and select Save. Trace the flow to determine why neither inline validation nor a save error is shown; done means invalid usernames produce a clear warning or error and account creation failures are explained to the user.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100