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

Handle apollo errors correctly #1660

Open
ztefanie opened this issue Oct 2, 2024 · 0 comments · May be fixed by #1878
Open

Handle apollo errors correctly #1660

ztefanie opened this issue Oct 2, 2024 · 0 comments · May be fixed by #1878
Assignees
Labels

Comments

@ztefanie
Copy link
Member

ztefanie commented Oct 2, 2024

Is your feature request related to a problem? Please describe.
the function getMessageFromApolloError returns wrong error messages to the user. As a user I want to see correct error messages.

Describe the solution you'd like
The getMessageFromApolloError return the correct error message

Additional context

  • Go to ProjectSettingsController.tsx and removee the if case that is return an "missing rights" section.
  • Now login as bayern project admin
  • open http://localhost:3000/project
  • create a token
  • see the error message "Server nicht erreichbar."
    the backend return the correct error code "403 Forbidden". The user should get an appropriate information about the error that occured. This should not only happen for this example but everywhere.
@ztefanie ztefanie added the Task label Oct 2, 2024
@f1sh1918 f1sh1918 moved this to Next Up in entitlementcard Oct 7, 2024
@steffenkleinle steffenkleinle moved this to Next Up in team-app Oct 22, 2024
@f1sh1918 f1sh1918 self-assigned this Jan 21, 2025
@f1sh1918 f1sh1918 linked a pull request Jan 21, 2025 that will close this issue
@connium connium moved this from Next Up to In Progress in team-app Jan 23, 2025
@f1sh1918 f1sh1918 moved this from In Progress to In Review in team-app Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Review
Status: Next Up
Development

Successfully merging a pull request may close this issue.

2 participants