Enatega Admin: Location not getting added after saving a store.

Open
#1,909 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
frontend, web-dev

Research direction

Reproduce the flow in the Enatega Admin store form: add a store, save it, move to the location step, and save a location. Trace how the selected restaurant/store is carried between steps and verify that saving the location succeeds without the “No restaurant is selected” validation message.

Written by the indexing model from the issue text.

Description

Describe the bug
When we save a store and move on to location, the location is not getting added and gives a validation message that no restaurant is selected.

To Reproduce
Steps to reproduce the behavior:

Click on Add a store.
Fill in all the fields.
Click on save.
Observe that the form now heads to the next step i.e. location
Add a location gives a validation message that "No restaurant is selected"
Expected behavior
When adding location and saving it, it should saves the location without showing any validation message.

Desktop :

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.