Enatega Restaurant Application : Restaurant Closed/Opened toggle button not working properly also check the notification toggle too
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Start by reproducing the issue in the Enatega Restaurant application's Profile menu, checking both toggles and then reopening the application. Trace how each selected state is stored and restored; done means restaurant availability and notification settings remain accurate after closing and reopening the app.
Written by the indexing model from the issue text.
Description
Describe the bug
The "Restaurant Closed/Opened" toggle button is not functioning as intended. Specifically, when attempting to change the restaurant's status, the toggle does not respond or reflect the correct state. Additionally, the notification toggle button exhibits similar unresponsiveness, failing to enable or disable notifications as expected.
To Reproduce
Steps to reproduce the behavior:
Go to 'Enatega Restaurant application'
Click on 'Profile' menu button.
See error now change statuses closed or open than close the app , now again open the application the status is changed automatically similarly issue with notifications.
Expected behavior
Both toggle buttons should accurately reflect and change their respective states upon user interaction. The "Restaurant Closed/Opened" toggle should switch between "Closed" and "Opened" statuses, updating the restaurant's availability accordingly. The notification toggle should enable or disable notifications based on the user's selection.
Screenshots
Screen_Recording_20250128_115912.mp4
Smartphone (please complete the following information):
Device: [e.g. Infinix Hot 50]
OS: [e.g. Android ]
Browser [e.g. Application]
Version [e.g. Latest ]
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from lambertf917/milk-ordering-app-react
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
All issues in lambertf917/milk-ordering-app-react
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·