hector-jewell / hector-jewell/uber-eats-clone-using-react-native
Restaurants with High Delivery Charges Should Not Be Displayed Outside Delivery Area
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Some restaurants (e.g., Farm Fresh - Wadi Halfa) in the Enatega app have very high delivery charges due to their location being far from the user's delivery address. These restaurants should not be displayed if they lie outside the delivery premises or serviceable area.
To Reproduce
Open the Enatega app.
Set a delivery address that is far from certain restaurants (e.g., Delish Bites Co.).
Browse through the list of available restaurants.
Observe that some restaurants with high delivery charges are still displayed in the search results.
Expected behavior
Restaurants that fall outside the delivery service area or have prohibitively high delivery fees due to distance should not be displayed in the list of available restaurants.
Actual Behaviour
Restaurants that are located far from the delivery address are still displayed, despite the high delivery fee.
Screenshots
IMG_0482
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 file or test is named. First reproduce the issue in the Enatega app using a delivery address far from the example restaurants, then trace the restaurant listing/search flow and its delivery-area or fee data. Done means restaurants outside the serviceable area or exceeding the defined distance or fee limit no longer appear in available restaurant results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100