Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve success and error handling of API calls #1348

Open
2 tasks done
oyo opened this issue Nov 18, 2024 · 0 comments
Open
2 tasks done

Improve success and error handling of API calls #1348

oyo opened this issue Nov 18, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@oyo
Copy link
Contributor

oyo commented Nov 18, 2024

Description

As a portal user,
I want to get notified about API call responses,
so that i am informed whether my actions have been fulfilled correctly or not.

Acceptance Criteria

  • (all) API calls should display a success Notification that disappears after a short time
  • all API calls should display a error message in case of an error

Additional Information

Ref: eclipse-tractusx/sig-release#882
A generic approach would be using the Redux Toolkit middleware: https://redux-toolkit.js.org/rtk-query/usage/error-handling#handling-errors-at-a-macro-level
The Notifications can be shown using the existing NotificationService. However this implementation should be changed from a real queue with 7sec display time to individual timeouts for each message as success messages are supposed to disappear more quickly then errors.

@oyo oyo added the enhancement New feature or request label Nov 18, 2024
@oyo oyo self-assigned this Nov 18, 2024
@github-project-automation github-project-automation bot moved this to NEW USER REQUEST in Portal Nov 18, 2024
@MaximilianHauer MaximilianHauer moved this from NEW USER REQUEST to BACKLOG in Portal Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: BACKLOG
Development

No branches or pull requests

1 participant