marthaegrimaldi / marthaegrimaldi/zomato-clone-app-source-code
Rejected Orders from the Restaurant application are not displayed in the customer application.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
When an order is rejected by the restaurant, it disappears from the customer app without being recorded in the "My Orders" list or providing any notification to the customer.
**To Reproduce**
1. Place an order through the customer application.
2. Reject the order from the restaurant application.
3. Check for notifications or updates in the customer application.
4. Check the "My Orders" list in the customer application.
**Observed Behavior**
The rejected order disappears entirely from the app without any history or notification to the customer.
**Expected behavior**
1. The rejected order should appear in the "My Orders" list under a "Canceled" or "Rejected" section.
2. The customer should receive a notification about the rejection with a reason provided (if available).
3. Example notification: "Your order has been rejected by the restaurant due to [reason]. The order has been moved to your order history under 'Canceled Orders.' Please place a new order or contact support for assistance."
**Smartphone (please complete the following information):**
Device: iPhone15pro
OS: iOS17.6.1
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
No files, tests, or entry points are named. Start by tracing the order-rejection flow from the restaurant application into the customer application's My Orders view and notification handling. Done means rejected orders remain visible with a Canceled or Rejected status and the customer receives a rejection notification, including a reason when available.
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
- 35/100