No Restriction on Duplicate Restaurant Names Under the Same Vendor

Open
#723 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
backend

Research direction

No files or tests are named. Start by tracing the vendor restaurant creation flow and the restaurant name persistence or validation logic. Reproduce creation of two restaurants with the same name under one vendor, then verify that the duplicate is rejected with the requested validation message while the same name remains possible for different vendors.

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
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raymondjames090/food-ordering-system-java-eclipse

All issues in raymondjames090/food-ordering-system-java-eclipse

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.