marthaegrimaldi / marthaegrimaldi/zomato-clone-source-code

Enatega Admin Dashboard: Page refreshes and redirects to another vendor stores, while we are deleting a store from another vendor

Open
#668 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
1
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
When attempting to delete a store under a specific vendor, the page unexpectedly refreshes and redirects the user to a different vendor's store page. This occurs immediately after the delete action, causing confusion and misalignment in the store management workflow.

To Reproduce
Steps to reproduce the behavior:

Go to 'Enatega Admin Dashboard'
Click on 'Vendors' from general dropdown.
Now select a vendor, its stores will be showing up on right store
See error now delete a store you will see the page unexpectedly refreshes and redirects the user to a different vendor's store page. This occurs immediately after the delete action.
Expected behavior
The system should remain on Vendor A’s store list after deletion, showing the updated list without the deleted store.

multivendor-admin.enatega.com_general_vendors.-.Google.Chrome.2025-03-20.09-55-27.1.mp4
Desktop (please complete the following information):

OS: [e.g. Windows]
Browser [e.g. chrome]
Version [e.g. Latest]

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in the Enatega Admin Dashboard through Vendors: select a vendor, open its stores, and delete one. Trace the page refresh and redirect after deletion; done means the view remains on the selected vendor and shows its updated store list without the deleted store. No source files or tests are named in the issue.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.