Better Error System #52
Description
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