Enatega Customer Application : On the discovery screen, the number of restaurants displayed is greater than the number of restaurants shown on the dedicated restaurants screen
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react-native
- Domain
- frontend, mobile-dev
Research direction
Reproduce the mismatch in the Enatega Customer Application by comparing the Discovery and Restaurants screens with the same data or filters. Trace how each screen obtains and counts restaurants, then verify that both displayed totals match for the same conditions. Done means the two screens consistently show the same restaurant count.
Written by the indexing model from the issue text.
Description
Describe the bug
On the discovery screen, the number of restaurants displayed is greater than the number of restaurants shown on the dedicated restaurants screen. This inconsistency leads to confusion for users and impacts their experience when browsing the app.
To Reproduce
Steps to reproduce the behavior:
Go to 'Enatega Customer Application'
Now compare both screens Discovery vs Restaurants.
3.See that number of restaurants on discovery screen are more than the restaurants on restaurants screen.
Expected behavior
The number of restaurants displayed on the discovery screen should match the number displayed on the restaurants screen for the same set of data or filters.
Screenshots
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
- 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/ubereats-clone-app-using-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/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 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
All issues in lambertf917/ubereats-clone-app-using-react-native
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