Enatega Customer Application Bug in Order History
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript, react-native
Research direction
Start by reproducing the issue in the Enatega Customer Application through a restaurant order, then inspect the Order History under Profile > My Orders and trace how Current Orders and order numbers are selected. Done means the in-progress order appears with its own matching order number rather than the old “The Dessert Table” order.
Written by the indexing model from the issue text.
Description
Describe the bug
Enatega Customer Application Bug in Order History , when customer places an order from any of the restaurants and after that went to check order history the order history keep showing the details of an very old order from the restaurant name 'The Dessert Table' and Also when places a new order it changes the current order number of with previous order number.
To Reproduce
Steps to reproduce the behavior:
Go to 'Enatega Customer Application '
Click on any of the restaurant.
Place an order.
Go to profile menu button. Then select Order History under My Orders check Current Orders details and match its order number with your order which is in progress.
Expected behavior
Under Current Order there should be shown the current/in progress orders not previous orders and also the order must be correct match with current order details .
Screen Recording
WhatsApp.Video.2025-01-15.at.11.49.12.AM.mp4
Smartphone (please complete the following information):
Device: [e.g. Infinix Hot 50]
OS: [e.g. Android]
Browser [e.g. Application]
Version [e.g. 22]
- Dominant language
- JavaScript
- Stars
- 2
- 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 patriciaperez90/react-native-based-uber-eats-clone-app
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
patriciaperez90/react-native-based-uber-eats-clone-app#2622 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
patriciaperez90/react-native-based-uber-eats-clone-app#2620 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
patriciaperez90/react-native-based-uber-eats-clone-app#2564 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patriciaperez90/react-native-based-uber-eats-clone-app#2558 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patriciaperez90/react-native-based-uber-eats-clone-app#2557 ·
All issues in patriciaperez90/react-native-based-uber-eats-clone-app
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