gray-mueller / gray-mueller/open-source-delivery-app

Lack of Confirmation Message After Saving Restaurant Location

Open Beginner friendly
#320 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Description:
Users are encountering a significant issue on the website when inputting a restaurant's location. After making changes to the restaurant's location details and saving them, the platform fails to display a confirmation message. This lack of feedback leaves users uncertain about whether their changes have been successfully saved, potentially causing confusion and the need for users to double-check their actions.

Steps to Reproduce:

Log in to the website on a compatible device.
Access the restaurant's location settings or editing section.
Make changes to the restaurant's location details.
Save the changes.
Observe the screen for any confirmation message.
Expected Result:
After making changes to the restaurant's location details and saving them, users should receive a confirmation message indicating that their changes have been successfully saved. This feedback is important to ensure that users are aware of the status of their actions.

Actual Result:
Users find that, after saving changes to the restaurant's location, the platform does not display any confirmation message. This issue leaves users uncertain about whether their changes were saved, potentially leading to confusion and the need for additional verification.

Impact:
This issue has a moderate negative impact on the user experience, as it can lead to uncertainty and potential double-checking of actions. Users should have clear feedback regarding the successful application of changes to the restaurant's location.

image

Activity

Contributor guide

Open the contributing guide

Research direction

Start at the restaurant location settings or editing entry point described in the issue and trace the save action. Check how nearby settings pages show success feedback, then ensure a confirmation appears after the location changes are saved and verify the reported reproduction steps.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.