When creating an expense or a compensation an HTTP-error of type 406 might be thrown (see expense-specification and compensation-specification for details) but there is no code handling this specific error in the web client. This in turn leads to confusing behaviour when trying to add an expense violating the constraints of the endpoint.
When creating an expense or a compensation an HTTP-error of type 406 might be thrown (see expense-specification and compensation-specification for details) but there is no code handling this specific error in the web client. This in turn leads to confusing behaviour when trying to add an expense violating the constraints of the endpoint.
See issue on teiler.api.io for further details.