lambertf917 / lambertf917/react-native-uber-eats-clone
Non-functional Addon Option in Need of Repair in Enateg Multivendor customer web.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Issue: Non-functional Addon Option in Need of Repair in Enateg Multivendor customer web.
Description:
The addon option within web is currently non-functional. It should ideally pop up and allow users to select and configure additional options, with corresponding price adjustments. However, this feature is not working as intended.
Impact:
User Frustration: Users may experience frustration when they cannot add and customize addons for their orders.
Inaccurate Pricing: The malfunctioning addon option can lead to incorrect pricing and order details.
Steps to Reproduce:
Access the customer web.
Attempt to utilize the addon option when placing an order.
Observe that the addon option does not work as expected.
Expected Resolution:
You should address the non-functional addon option in the application, making it functional as intended. Users should be able to easily add and customize addons with corresponding price adjustments. This is essential for order accuracy and a positive user experience.
Screenshot 2023-10-19 140836
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 addon flow in the customer web while placing an order, then trace the existing addon option entry point and its pricing behavior. Done means users can open the addon option, select and configure additions, and see corresponding price adjustments reflected in the order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100