marthaegrimaldi / marthaegrimaldi/meal-ordering-app-using-react-native
Negative Values Allowed in Discount, Tip, Price and Addons Fields
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Description:
During testing of the Enatega Multivendor Admin Dashboard, a critical issue was identified where fields such as discount, tip, price and addons allow the entry of negative values. This behavior is inconsistent with standard practices and poses a risk to accurate financial calculations, potentially leading to incorrect order totals and financial discrepancies.
Steps to Reproduce:
Log in to the Enatega Multivendor Admin Dashboard.
Navigate to sections where fields for discount, tip, price or addons are present.
Attempt to enter a negative value (e.g., "-10") in any of these fields.
Expected Behavior:
The application should restrict the entry of negative values in fields related to financial transactions, such as discount, tip, price and addons. An error message or validation prompt should be displayed, indicating that negative values are not allowed.
Actual Behavior:
The application allows the entry of negative values in fields such as discount, tip, price and addons without providing any error or validation message.
image
image
image
image
Activity
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 in the Enatega Multivendor Admin Dashboard by reproducing the issue in the discount, tip, price and addons fields, then locate their validation entry points. Done means negative values are rejected in each field and an error or validation prompt is displayed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100