Vendor Page Store Counter Does Not Increment Beyond 100
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react-native
- Domain
- frontend
Research direction
Start at the admin dashboard's Vendor page and reproduce the store-creation flow through the 101st store. Trace where the counter or store limit is enforced, then verify the intended behavior for counts above 100. Done means stores can be added beyond 100, or an intentional limit produces a clear message.
Written by the indexing model from the issue text.
Description
Describe the bug
On the admin dashboard's "Vendor" page, while adding a new store, the store count does not increment beyond 100. This prevents vendors from registering more than 100 stores, even if the system should allow it.
To Reproduce
Steps to reproduce the behavior:
Go to the "Vendor" page in the admin dashboard.
Attempt to add stores until the count reaches 100.
Try adding the 101st store.
Observe that the counter does not increase and the store is not added.
Expected behavior
The system should allow vendors to add more than 100 stores if there is no set limit, or at the very least, display a clear message if a limit is intentionally enforced.
Screenshots
Image
Desktop (please complete the following information):
OS: [e.g., Windows 10]
Browser: [e.g., Chrome]
Version: [e.g., 112]
Additional context
There is no visible warning or error indicating that the limit has been reached. This may be a front-end limitation or a hardcoded cap that needs to be reviewed or adjusted.
- 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 lambertf917/ubereats-clone-app-using-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
All issues in lambertf917/ubereats-clone-app-using-react-native
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