Better Error System - Githubissues

WYVERN2742 commented 2 years ago

Right now, the error system is a mess and does not cover all scenarios.

The error system should be redone alongside the validation system in order to clearly indicate to the user what has gone wrong. Validation should preemptively prevent any user-side inputs that will cause errors to the backend.

Some examples:

Currently, broken configuration files do not show any indicator during import
When the backend server is down, errors flood the UI since each component fails to transmit
Too fine-grained response from the server doesn't need to say exactly what paramater caused an error

WYVERN2742 commented 6 months ago

"PUT /material/set HTTP/1.1" 200

Has no failure case, issues saving new materials are not propagated to frontend

WYVERN2742 commented 3 months ago

Much work done towards this on the backend side with #82

Still require work on the frontend, and error recovery (such as #81)

WebxCT / WebCT

Better Error System #52