Enatega Admin: When creating a sub-category in a store, the success message is wrong

Open Beginner friendly
#1,890 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
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript, react-native
Domain
frontend

Research direction

Reproduce the issue through the admin store's Product Management > Categories flow and inspect the sub-category creation success notification entry point. The change is done when creating a sub-category shows the correct success title rather than "Delete Sub category", while retaining the successful-creation message.

Written by the indexing model from the issue text.

Description

Describe the bug
when creating sub category in a store, the success message states that "Delete Sub category" as a title.

To Reproduce
Steps to reproduce the behavior:

Open admin
go to a store.
open the "categories" in "product management".
create sub category.
observe that success message states that "Delete sub category" and "Created sub category successfully"
Expected behavior
It should not state "Delete sub-category" as a title of the success message.

Desktop (please complete the following information):

OS: [windows]
Browser [chrome]

Labels: Enatega Multivendor Admin Dashboard, Bug

Dominant language
JavaScript
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 raymondjames090/uber-eats-app-clone-using-react-native

All issues in raymondjames090/uber-eats-app-clone-using-react-native

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.