No Restriction on Duplicate Restaurant Names Under the Same Vendor
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, react-native
Research direction
Start by locating the restaurant creation flow and its validation or persistence logic. Reproduce the steps with two restaurants sharing a name under one vendor, then add the requested restriction and clear validation message. Done means the duplicate is rejected while the same name remains usable under a different vendor.
Written by the indexing model from the issue text.
Description
Describe the bug
Currently, the system allows creation of multiple restaurants with the same name under the same vendor account. This can lead to confusion, data conflicts, and operational issues. There is no validation or message indicating that the restaurant name already exists.
To Reproduce
Steps to reproduce the behavior:
Log in as a vendor
Create a restaurant/store with a specific name (e.g., "Tasty Bites")
Attempt to create another restaurant with the same name under the same vendor account
Observe that the system allows it without any warning or error
Expected behavior
There should be a restriction in place to prevent creating duplicate restaurant names under the same vendor. The system should display a clear validation message like:
"A restaurant with this name already exists."
Screenshots
Image
Desktop (please complete the following information):
OS: Windows 11
Browser: Chrome
Version: [e.g., 123.0.6312.86]
Additional context
This issue may affect order routing, reporting, and user management. Implementing this validation would help maintain data integrity and improve user experience for vendors managing multiple stores.
- Dominant language
- JavaScript
- Stars
- 2
- 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 patriciaperez90/react-native-based-uber-eats-clone-app
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
patriciaperez90/react-native-based-uber-eats-clone-app#2622 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
patriciaperez90/react-native-based-uber-eats-clone-app#2620 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
patriciaperez90/react-native-based-uber-eats-clone-app#2564 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patriciaperez90/react-native-based-uber-eats-clone-app#2558 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patriciaperez90/react-native-based-uber-eats-clone-app#2557 ·
All issues in patriciaperez90/react-native-based-uber-eats-clone-app
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