Task: Wrap Backend errors In Frontend Errors

[n3rdc4ptn]

Understand the Task

Description

Currently we show errors from the backend to the user directly (e.g. flux component). We should check where we do this, and prevent this.
We should only show errors defined in the frontend. Further details and the backend error text can then be put into the console for now.

Any further valuable resources.

No response

What is required to accept the Task as done.

Done Criteria

• error enum in frontend for common Http Codes
  • User Errors
    • Bad Input (if user has done something wrong)
    • NotAuthorized (if user has no access to the resource he/she tries to access)
    • NotAuthenticated (if user is no longer logged in or has no account)
  • ServerErrors (Server behaved unexpected)
    • No Result (show full error in console, only display a no result message, can also be merged with next error InvalidResult)
    • Invalid Result (show full error in console, only display, that the response format is invalid)
    • ErrorFromServer (server returned error, we should not show the real error, but that a server Error happened. Show the full message in console)
• Frontend should use the enum everywhere errors can happen; if backend interaction happen, errors should be wrapped or transformed into these enum errors

Use Case

• No access to parent Project or Workspaces
• Received Deep link to an MCP but dont have access