Proper default handling of custom backend errors/warnings by API
We recently introduced an error wrapper in the pipelines API, soon to follow as a middleware in the nacsos-core API. This enables us to improve the on-error communication between backend and frontend.
Ideally, the default responseTransform1 handles these error types properly. Especially by defining the (custom) errors that are potentially raised by the backend as a type or dataclass. Should the default behaviour also emit a ToastEvent with the error info?