Language Inconsistency in Commission Rate Notification Popup in Enatega Multivendor Admin Dashboard

Open Beginner friendly
#101 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript

Research direction

Reproduce the issue in the Enatega Multivendor Admin by changing the language, editing commission rates, and saving them. Locate the commission-rate save notification and the existing localization resources; done means the success popup uses the selected language instead of English, with the reproduction steps verified again.

Written by the indexing model from the issue text.

Description

Describe the bug
A language inconsistency has been identified in the Enatega Multivendor Admin dashboard. After changing the language and saving commission rates, the notification popup indicating the successful save of commission rates remains in English, causing a discrepancy in the user interface.

To Reproduce
Steps to reproduce the behavior:

Log in to the Enatega Multivendor Admin.
Change the language setting to a language other than English.
Navigate to the commission rates section.
Modify the commission rates and save the changes.
Observe that the notification popup confirming the successful save remains in English instead of switching to the selected language.
Expected behavior
The notification popup confirming the successful save of commission rates should be displayed in the selected language, ensuring a consistent user experience.

Screenshots

123.mp4
Desktop:

Browser: chrome

Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

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.

More from gray-mueller/full-stack-document-solution

All issues in gray-mueller/full-stack-document-solution

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.