Consider changing the serverRequest function to throw

[karifrederiksen]

Currently the serverRequest function returns a union or either { isOk: true; data: ... } or { isOk: false; status: ...; genericErrors: ...; fieldErrors: ... }. I've noticed however that in many cases when isOk == false we often return an empty view, sometimes throw the error, and sometimes don't even check if there was an error. It seems this explicit approach to error handling is leading to bad practices, so I think we should change serverRequest to throw an error instead.

The error can then be caught and handled by a generic error boundary component which we wrap around arbitrary points in the application.

(also, I wonder, does react do anything when errors are thrown inside onClick handlers, or are they ignored?)

[karifrederiksen]

Turns out there are 27 references to this function. so it's a bit too much to change at once. I think I'll just introduce a second version of it that does throw when it encounters an error, and then we can gradually replace references to the current version with the new one.

There are probably also some cases where the current serverRequest is superior because it can't throw, so maybe we should keep both and just pick the appropriate one for each situation.

[LinusPhoenix]

Your current work on this will be included in 0.2.5, do you want me to keep this open or can this be closed?