chore: add restart button for generic route error component#489
Merged
Conversation
4cde4f9 to
d2aa4d3
Compare
achou11
added a commit
that referenced
this pull request
Jan 19, 2026
When some generic route error occurs, we typically display a panel containing information about the error and a button that reloads the page. However, there are cases where you can get stuck on the page due to UI elements being intentionally disabled. Now we provide a "restart" button which doesn't restart the application entirely, but just loads the "index" page as opposed to the current page, which is usually sufficient. Might be worth using different wording eventually, especially if we introduce something that actually restarts the application.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When some generic route error occurs, we typically display a panel containing information about the error and a button that reloads the page. However, there are cases where you can get stuck on the page due to UI elements being intentionally disabled.
Now we provide a "restart" button which doesn't restart the application entirely, but just loads the "index" page as opposed to the current page, which is usually sufficient. Might be worth using different wording eventually, especially if we introduce something that actually restarts the application.