gray-mueller/food-delivery-applications-using-react-native

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

Open

#180 opened on Mar 22, 2025

View on GitHub
 (0 comments) (0 reactions) (0 assignees)JavaScript (0 forks)auto 404
Enatega Multivendor Admin DashboardHigh Prioritybuggood first issue

Repository metrics

Stars
 (0 stars)
PR merge metrics
 (PR metrics pending)

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:

  1. Go to 'Enatega Admin Dashboard'
  2. Click on 'Vendors' from general dropdown.
  3. Now select a vendor, its stores will be showing up on right store
  4. 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.

Desktop (please complete the following information):

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

Contributor guide

Research direction
Inspect the delete store handler and the routing logic that triggers after deletion. Check if there's a navigation redirect that incorrectly uses a global store ID or vendor ID instead of the current context.
Tech stack
javascriptreact
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitReact
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75