Skip to content

Conversation

@LukasHirt
Copy link
Collaborator

Description

We've added a crash page to the application. This page is displayed when the application encounters an error that it cannot recover from. The first such error we are catching is when spaces loading fails.

Motivation and Context

Handle errors that the app cannot recover from instead of showing the UI in a "stuck" state.

How Has This Been Tested?

  • test environment: macos v26.2, chrome v143.0.7499.170
  • test case 1: trigger API error when loading spaces

Screenshots (if appropriate):

image

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Technical debt
  • Tests
  • Documentation
  • Maintenance (e.g. dependency updates or tooling)

@LukasHirt LukasHirt self-assigned this Dec 30, 2025
We've added a crash page to the application. This page is displayed when
the application encounters an error that it cannot recover from.
The first such error we are catching is when spaces loading fails.
@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
0.0% Condition Coverage on New Code (required ≥ 50%)
1 New Bugs (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@LukasHirt LukasHirt marked this pull request as draft December 30, 2025 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants