marthaegrimaldi / marthaegrimaldi/food-ordering-application-using-react-native
Enatega Customer Application Bug in Order History
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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]
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 by reproducing the steps through a restaurant, checkout, the profile menu, and Order History. Trace how Current Orders and the order number are populated; done means the in-progress order is shown with its own matching details rather than the old The Dessert Table order.
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