Name Textbox in Profile Menu Accepts Spaces and Special Characters
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start by locating the profile menu's name textbox implementation in the Enatega app or website and reproduce the behavior with spaces and characters such as @, #, and !. Define the accepted name characters, including whether apostrophes and hyphens are allowed, then verify that disallowed input is rejected while valid names continue to work.
Written by the indexing model from the issue text.
Description
Describe the bug
The name textbox in the profile menu tab of the Enatega app/website is accepting spaces and special characters, which should not be allowed. The textbox should only accept valid characters, such as letters, and possibly specific symbols (e.g., apostrophes or hyphens).
To Reproduce
Open the Enatega app/website.
Go to the profile menu tab.
Click to edit the name field (e.g., during profile update).
In the name textbox, type a name with spaces or special characters (e.g., "@", "#", "!", etc.).
Observe that the textbox allows spaces and special characters as valid input.
Expected behavior
The name textbox should only accept valid characters such as alphabetic characters and, if necessary, a few special characters like apostrophes or hyphens.
Special characters (e.g., "@", "#", "!", etc.) and extra spaces should be rejected, ensuring proper data input.
Actual Behavior
The name textbox in the profile menu accepts spaces and special characters, which could lead to invalid or inconsistent data in the profile.
Screenshots
https://github.com/user-attachments/assets/80492f02-544b-4c24-a5fb-cd60d8ea1eba
Smartphone (please complete the following information):
Device: iPhone15pro
OS: iOS17.6.1
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from raymondjames090/food-ordering-system-java-eclipse
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
All issues in raymondjames090/food-ordering-system-java-eclipse
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100