Margaret-Petersen / Margaret-Petersen/python-based-food-ordering-system
No Restriction on Duplicate Restaurant Names Under the Same Vendor
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
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 duplicate-name flow for two restaurants under one vendor, then locate the restaurant creation entry point and any related validation or persistence tests. The work is done when duplicate names are rejected only within the same vendor, a clear validation message is shown, and names remain allowed under different vendors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100