marthaegrimaldi / marthaegrimaldi/restaurant-ordering-platform-with-source-code
Conflicting Success and Error Messages When Updating Bank Details on Bank Management Page
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
On the Bank Management page, when a user updates their bank information, two messages are shown:
An error message indicating the update was unsuccessful.
A success message indicating the bank details were updated successfully.
This creates confusion about whether the update actually went through.
To Reproduce
Steps to reproduce the behavior:
Open the Bank Management page in the app.
Edit and update the bank account information.
Tap the Update button.
Observe that both a success and an error message are displayed simultaneously or in quick succession.
Expected behavior
Only one appropriate message should appear based on the actual outcome. If the update is successful, only the success message should display. If it fails, only the error message should be shown.
Screenshots
Image
Smartphone (please complete the following information):
Device: Samsung A15
Additional context
This may be due to duplicate response handling in the frontend logic or inconsistent API feedback. It should be resolved to prevent confusion and ensure clear user communication.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Bank Management page and follow the Update button into the frontend response handling for bank-information changes. Reproduce the issue on a Samsung A15 or equivalent device and inspect the API feedback path. Done means a successful update shows only a success message, while a failed update shows only an error message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, payments
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100