lambertf917 / lambertf917/food-ordering-system-source-code
Address Field Accepts Numbers-Only Input – Should Require Alphanumeric Format
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
The address field is currently accepting inputs that contain only numbers (e.g., "12345") as valid addresses. While it does allow letters as well, it should not accept purely numeric input, since a valid address typically includes both letters and numbers (e.g., street names).
To Reproduce
Steps to reproduce the behavior:
Navigate to a form with the address field (e.g., store creation or user profile)
Enter a numeric-only value such as "12345" into the address field
Submit the form
Observe that the form is accepted without any validation error
Expected behavior
The address field should require at least one alphabetical character in addition to numbers. It should not allow submission if the input is numbers-only.
Screenshots
Image
Desktop (please complete the following information):
OS: Windows 11
Browser: Chrome
Additional context
Allowing numbers-only input can lead to invalid or unusable address data. Implementing proper validation to enforce a realistic address format will improve data quality and system reliability.
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 with the address fields in the store creation and user profile forms, then reproduce the issue using a numeric-only value such as "12345". Trace where submission validation is applied and update the address rule so numeric-only input is rejected while values containing letters are accepted. Verify the behavior in both mentioned form entry points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100