Negative Values Accepted in Enatega Multivendor Admin Dashboard Fields
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in the Enatega Multivendor Admin dashboard and reproduce the issue in the dashboard or relevant section using Chrome. Identify which fields accept negative values, then trace their input validation and submission path. Done means inapplicable negative values are rejected with an error and valid values still submit correctly.
Written by the indexing model from the issue text.
Description
Describe the bug
A bug has been identified in the Enatega Multivendor Admin dashboard where negative values are being accepted in certain fields. This behavior can lead to inaccurate data representation and potential miscalculations. It is crucial to rectify this issue to ensure the reliability of the information presented in the dashboard.
To Reproduce
Steps to reproduce the behavior:
Log in to the Enatega Multivendor Admin.
Navigate to the dashboard or relevant section.
Attempt to input negative values in applicable fields (specify fields where negative values are accepted).
Observe that the system allows the entry of negative values without generating an error.
Expected behavior
Negative values should not be accepted in fields where they are not applicable. The system should validate the input and prevent the submission of negative values, providing an error message if attempted.
Screenshots
image
image
image
image
image
image
*Desktop:
Browser: chrome
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 patriciaperez90/document-solution-application-react
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
All issues in patriciaperez90/document-solution-application-react
Similar issues
-
freshness freshness:observed-only
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
thoroc/context-radar#282 ·
-
bug P2 rust
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area: web
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
gabe-santana/arkdraw#25 ·
-
bug require-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
expressjs/expressjs.com#2549 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug good first issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
codercops/discord-bot#101 · 1 comment ·
Maintainers usually reply within 1 day