Margaret-Petersen / Margaret-Petersen/uber-eats-clone-android
Customer App Review restaurant issues on discovery screen
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When the customer give reviews to any of the restaurant from the his past orders and the customer goes back to the discovery screen the REVIEW is not updated on front restaurant screen.
Another Scenario : The customer should be allowed to review order only once per order and after that he should not be allowed to again review the order again.
To Reproduce
Steps to reproduce the behavior:
Go to 'Customer Application' then select Profile menu button.
Click on 'Order History' under My Orders select Past.
Then give review any of the previous order rate it , then go back to discovery page and see the restaurant specifically the one you reviewed its changing the reviews until open that restaurant to the reviews.
Expected behavior
When a customer give reviews to a restaurant it should be displayed immediately on restaurant discovery page without tapping into the restaurant details.
Also allow only once to review per order.
Screen recording
WhatsApp.Video.2025-01-15.at.11.49.12.AM.1.mp4
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
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 source files or tests are named. Start by tracing the Customer Application's Order History review flow and the discovery screen's restaurant data refresh, then reproduce both scenarios from the issue. Done means a submitted review appears immediately on the discovery card and each order can be reviewed only once.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100