Enatega Customer App: For a specific restaurant cuisine name not showing up on its details card but showing when opening it up

Open

#813 opened on Jul 9, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 35/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: javascript, react-native
Domain: mobile

Research direction

No files or tests are named. Reproduce the issue in the Enatega Customer App discovery page using the restaurant "Desiree Wyatt", then compare the restaurant summary card with its full details page. Done means the cuisine name appears consistently in the summary card and details view.

Written by the indexing model from the issue text.

Description

Describe the bug
When viewing a restaurant's summary/details card (e.g., in a list or map view), the cuisine name is missing or not displayed. However, upon clicking into the full restaurant details page, the cuisine name appears correctly. This inconsistency may lead to confusion or a degraded user experience when browsing or filtering by cuisine type.

To Reproduce
Steps to reproduce the behavior:

Go to 'Enatega Customer App'
Now go to discovery page see there restaurant named "Desiree Wyatt".
See error When viewing a restaurant's summary/details card (e.g., in a list or map view), the cuisine name is missing or not displayed. However, upon clicking into the full restaurant details page, the cuisine name appears correctly.
Expected behavior
A clear and concise description of what you expected to happen.

Smartphone (please complete the following information):

Device: [e.g. Infinix Hot 50]
OS: [e.g. Android]
Browser [e.g. App]

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

Contributor guide

Open the contributing 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.