lambertf917 / lambertf917/react-native-uber-eats-clone
Enatega Customer iOS + Admin Dashboard : Cuisine names are overflowing beyond the image square's boundary, breaking the UI.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Cuisine names are overflowing beyond the image square's boundary, breaking the UI. Also restrict the user to enter cuisine names with some words limits so it should not breaks the boundary.
To Reproduce
Steps to reproduce the behavior:
Go to Enatega Customer application
Click on 'Restaurants' menu button.
Now see at the Top of screen restaurants see error Browse categories scroll-bar where Cuisine names are overflowing beyond the image square's boundary, breaking the UI.
Expected behavior
The cuisine names should stay within the image square and not overflow.
If the text is too long, it should either wrap properly or be truncated with "...".
The design should remain responsive for different screen sizes.
Screenshots
Image
Smartphone (please complete the following information):
Device: [e.g. iPhone13]
OS: [e.g. iOS18]
Browser [e.g. Application]
Version [e.g. latest]
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.
Research direction
Start in the Enatega Customer application at Restaurants > Browse categories, then check the related Admin Dashboard cuisine-name input. Reproduce the overflow with a long cuisine name on different screen sizes and inspect the components responsible for the image square and text. Done means long names wrap or truncate within the square and input length is limited without breaking the responsive layout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- frontend, mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100