feat/Client proper error handling #5

Open
opened 3 years ago by alban · 2 comments
alban commented 3 years ago
Owner

There are some unjustified unwraps in the code, mainly when querying the server. The case where there is any error should be handled by an error message in the browser.

There are some unjustified unwraps in the code, mainly when querying the server. The case where there is any error should be handled by an error message in the browser.
alban added the Feature label 3 years ago
alban self-assigned this 3 years ago
alban commented 3 years ago
Poster
Owner

There is an issue in Sycamore aiming to make fallible components a thing. That could be a step towards proper error handling.
In the meantime, the only possible runtime errors in the client are with fetching data from the API, which is unlikely.

There is an issue in Sycamore aiming to make fallible components a thing. That could be a step towards proper error handling. In the meantime, the only possible runtime errors in the client are with fetching data from the API, which is unlikely.
alban changed title from feat/Proper error handling to feat/Client proper error handling 3 years ago
alban commented 3 years ago
Poster
Owner

The update to Perseus beta.21 introduced error views, views that will be shown when issues occur, including critical errors when the wasm program panics. The error messages exist in the app right now but they look really bad.

The update to Perseus beta.21 introduced error views, views that will be shown when issues occur, including critical errors when the wasm program panics. The error messages exist in the app right now but they look really bad.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: alban/fast-insiders#5
Loading…
There is no content yet.