Margaret-Petersen / Margaret-Petersen/uber-eats-clone-using-react-native

Enatega Customer Application : Food banners are not showing up properly when there are 4 or above banners

Open
#871 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
Food banners are not showing up properly when there are 4 or above banners. When we add more than 4 banners from admin side on customer application , when one banner is showing up the next banner is also showing up already due to image sizes or else something.

To Reproduce
Steps to reproduce the behavior:

Go to 'Enatega Customer Application'
Now stay on discovery screen and observe the food banners you will see the issue.
Expected behavior
The food banners should up perfectly one banner at a time.

Screenshots

Screen_Recording_20250123_102526.mp4
Smartphone (please complete the following information):

Device: [e.g. Infinix Hot 50]
OS: [e.g. Android]
Browser [e.g. Application]
Version [e.g. 14]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the Enatega Customer Application on the discovery screen and reproduce the issue with four or more food banners configured from the admin side. Compare the behavior with the attached screen recording; done means the banners display one at a time without the next banner appearing early.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react-native
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.