Enatega Customer Application + Admin Dashboard: When status for a restaurant is closed from Admin it should be displayed on app with CLOSED clear indication.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react-native
Research direction
Reproduce the issue by marking a restaurant closed in the Enatega Admin Dashboard, then checking the customer application. Trace how the restaurant status is passed from the dashboard to the app; done means the restaurant remains visible with a clear CLOSED indication.
Written by the indexing model from the issue text.
Description
Describe the bug
Restaurant Marked as Closed in Admin Not Showing "CLOSED" Status in App.
To Reproduce
Steps to reproduce the behavior:
Go to 'Enatega Admin Dashboard'
Click on stores and mark status for any of the restaurants as Closed.
Now see error that the specific restaurant you closed will not be showing up on the app, it should be displayed on app with CLOSED clear indication.
Expected behavior
A restaurant with a closed status from admin should be displayed on app with CLOSED clear indication.
Desktop (please complete the following information):
OS: [e.g. Windows]
Browser [e.g. chrome, ]
Version [e.g. Latest]
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
- JavaScript
- Stars
- 2
- 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 patriciaperez90/react-native-based-uber-eats-clone-app
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
patriciaperez90/react-native-based-uber-eats-clone-app#2622 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
patriciaperez90/react-native-based-uber-eats-clone-app#2620 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
patriciaperez90/react-native-based-uber-eats-clone-app#2564 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patriciaperez90/react-native-based-uber-eats-clone-app#2558 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patriciaperez90/react-native-based-uber-eats-clone-app#2557 ·
All issues in patriciaperez90/react-native-based-uber-eats-clone-app
Similar issues
-
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 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100