Unintended Toggling of Buttons in "Restaurants Section" Section of Admin Dashboard
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start by reproducing the issue in the Admin Dashboard's Restaurants section using Chrome, then trace the toggle handling for the affected restaurant controls. Confirm that changing one button leaves neighboring buttons unchanged. Done means the reported unintended toggling no longer occurs and the expected behavior is verified in the dashboard.
Written by the indexing model from the issue text.
Description
Describe the bug
In the Enatega Multivendor Admin Dashboard, specifically in the "Restaurants section" section, there is an issue where toggling one button on or off intermittently triggers the system to toggle other buttons that were not intended to be changed. This behavior is unexpected and can lead to unintended changes in the settings of restaurants, causing potential confusion and errors in the admin interface.
To Reproduce
Steps to reproduce the behavior:
Log in to the Enatega Multivendor Admin Dashboard.
Navigate to the "Restaurants section" section.
Attempt to toggle a specific button (e.g., enable/disable a feature) for a restaurant.
Observe that other buttons in the vicinity may also be toggled without explicit user interaction.
Expected behavior
Toggling one button in the "Restaurants" section should only affect the state of that specific button, and other buttons should remain unchanged unless explicitly modified by the user.
Desktop:
Browser: chrome
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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/document-solution-application-react
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
All issues in patriciaperez90/document-solution-application-react
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
microsoft/playwright#43640 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
grasshopper-protocol/grsshppr#172 ·
Maintainers usually reply within 1 day
-
bug help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Tencent/teamai-cli#1397 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
DouyinFE/semi-design#3641 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day