Skip to content

Review Error handling after refactoring #174

Description

@dcoa

Description

There are a few areas where the error messages could be improved. There is important to make an analysis of all the current places errors needs to be displayed and how they should be displayed (Toast, other element such as the Error Page or an Alert)

For example, when a user does not have access to any course or library (an edge case), the application displays a generic error message instead of indicating that the user lacks the required permissions or access.

Steps to Reproduce

  1. Log in with a user account that does not have access to any course or library.
  2. Navigate to the application.
  3. Observe the error message displayed.

Actual Behavior

A generic error message is displayed.

Expected Behavior

The application should display a more specific error message indicating that the user does not have access to any courses or libraries, rather than showing a generic error. This would provide clearer feedback and help users better understand the reason for the failure.

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions