gray-mueller / gray-mueller/food-delivery-platform-for-restaurants-using-python
Customer App and Restaurant Enatega - Please define the purpose of timer here, as the timer gets to "0", then there should be something happening to that particular order
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When the user has placed the order, then after some time if the Restaurant hasn't accepted the order then the order should be removed from Restaurant side and there should be a cancellation notification or something like that on customer app side and the order should be removed.
To Reproduce
Steps to reproduce the behavior:
Go to 'Enatega Customer App'
Go to Restaurants menu button and select any restaurant.
Add to cart and Place an order
See error When the user has placed the order, then after some time if the Restaurant hasn't accepted the order then the order should be removed from Restaurant side and there should be a cancellation notification or something like that on customer app side and the order should be removed.
Expected behavior
When the user has placed the order, when the receiving time is out and if the Restaurant hasn't accepted the order then the order should be removed from Restaurant side and there should be a cancellation notification or something like that on customer app side and the order should be removed.
Smartphone (please complete the following information):
Device: [e.g. Infinix Hot 50]
OS: [e.g. Windows]
Browser [e.g.Application]
Version [e.g. 14]
Contributor guide
Research direction
Start by tracing the timer and order flow in the Enatega Customer App and the restaurant side, focusing on what happens when the timer reaches 0. Confirm how an unaccepted order is removed and how cancellation is communicated to the customer; done means both sides reflect the cancellation consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100