Enatega SingleVendor Admin Allowing Negative Values in Discount, Stock, and Price Fields
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript
- Domain
- frontend
Research direction
Start in the product management area of the Enatega SingleVendor Admin system and locate the editable discount, stock, and price fields. Inspect how these inputs currently validate values and check whether related fields use the same behavior. Done means negative values are rejected for these fields while valid values remain usable; reproduce the reported steps in Chrome to verify the result.
Written by the indexing model from the issue text.
Description
Describe the bug
I have identified a critical issue in the Enatega SingleVendor Admin system where it currently allows users to input negative values in fields related to discount, stock, price, and potentially other crucial parameters.
To Reproduce
Steps to reproduce the behavior:
Log in to the Enatega SingleVendor Admin system.
Navigate to the product management section or any relevant area where discount, stock, or price fields are editable.
Attempt to input a negative value in the discount, stock, or price fields.
Expected behavior
Log in to the Enatega SingleVendor Admin system.
Navigate to the product management section or any relevant area where discount, stock, or price fields are editable.
Attempt to input a negative value in the discount, stock, or price fields.
Screenshots
image
Desktop:
Browser : chrome
Additional context
Please investigate and address this issue promptly to ensure the Enatega SingleVendor Admin system maintains a high level of reliability and accuracy in data processing.
Thank you for your attention to this matter.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from raymondjames090/uber-eats-app-clone-using-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2069 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2003 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raymondjames090/uber-eats-app-clone-using-react-native#2002 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#1979 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
raymondjames090/uber-eats-app-clone-using-react-native#1978 ·
All issues in raymondjames090/uber-eats-app-clone-using-react-native
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100