hector-jewell / hector-jewell/uber-eats-clone-using-react-native
Optional Message in Customer App Not Fetched by Restaurant App
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
In the Enatega Multivendor Restaurant App, the optional message field in the Customer App is not being fetched by the Restaurant App. This issue affects communication between customers and restaurants, potentially leading to misunderstandings or incomplete orders.
To Reproduce
Open the Customer App.
Navigate to the order placement screen.
Enter an optional message in the designated field.
Place the order.
Open the Restaurant App.
Locate the order placed by the customer.
Check the order details for the optional message.
Expected behavior
The optional message entered by the customer should be visible in the order details in the Restaurant App.
Screenshots
Untitled.video.-.Made.with.Clipchamp.mp4
Smartphone (please complete the following information):
Device: IOS & Android
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 by reproducing the order flow from the Customer App to the Restaurant App, then trace where the optional message is included in the order and where restaurant order details are populated. Done means a message entered by the customer is visible in the corresponding restaurant order on both iOS and Android; verify with the reproduction steps and the attached video.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100