Handle Errors Gracefully
Closed this issue · 1 comments
antheas commented
Right now, if there is an error in the UI, it is not caught and the browser displays an error.
There should be a topmost container handling the errors, or preferably, a per-setting container that only disables a particular broken setting (the per-setting container can wrap the render child function, it does not have to be per setting type).
aarron-lee commented