lambertf917 / lambertf917/react-native-uber-eats-clone

Commission Rates Saving Issue with Missing Status in Enatega Multivendor Admin

Open Beginner friendly
#2,207 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
3
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Description:
When attempting to save commission rates in the Enatega Multivendor Admin, the rates are successfully saved; however, there is no corresponding status displayed, creating ambiguity for users. This lack of status information makes it challenging for administrators to verify whether the changes were applied successfully or if there were any errors during the process.

Steps to Reproduce:
Log in to the Enatega Multivendor Admin.
Navigate to the section for managing commission rates.
Modify or set new commission rates.
Save the changes.

Expected Behavior:
After saving the commission rates, a status message should be displayed confirming the successful update. This status information is crucial for administrators to ensure that their changes were applied as intended.

Actual Behavior:
Commission rates are saved successfully, but there is no accompanying status message, leaving users uncertain about the outcome of the operation.

13.12.2023_14.47.23_REC.mp4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the save flow in the Enatega Multivendor Admin and locate the commission-rates management screen and its save action. Verify the behavior when rates are changed and saved; done means administrators see a clear status message confirming success or reporting an error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react-native
Domain
frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.