Enatega Customer App: Incorrect Layout Displayed – Restaurant Layout Shown for Store Selected from Map View
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start at the Customer App's Store screen and trace the Map View store-marker selection into the screen it opens. Compare that path with normal store navigation; done means selecting a map store shows its store-specific categories, product lists, filters, and UI sections rather than the restaurant layout.
Written by the indexing model from the issue text.
Description
Describe the bug
When the user navigates to the Store screen and views store locations on the map, clicking on any store from the map view opens the restaurant layout instead of the store layout. This causes confusion and misrepresents the content, as store-specific elements (such as categories, filters, and UI sections) are replaced with restaurant-specific components.
Steps to Reproduce:
Open the application and navigate to the Store screen.
Switch to Map View to see the stores on the map.
Tap on any store icon or marker from the map.
Observe the screen that opens after selection.
Expected behavior
Selecting a store from map view should open the correct store layout, showing store-specific categories, product lists, and UI elements (e.g., “Grocery,” “Essentials,” or “Store Info”).
Smartphone (please complete the following information):
Device: [e.g. Infinix]
OS: [e.g. Android]
Browser [e.g. Application]
Version [e.g. 14 ]
Labels: Enatega Multivendor Customer App, High Priority, Bug
- 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 raymondjames090/food-ordering-system-java-eclipse
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
All issues in raymondjames090/food-ordering-system-java-eclipse
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