Currently, the Error model is unused, and the library just crashes whenever the web API sends an error. This should be resolved by throwing an exception containing the Error model when that happens, so users can catch that exception and handle it gracefully.
Currently, the Error model is unused, and the library just crashes whenever the web API sends an error. This should be resolved by throwing an exception containing the Error model when that happens, so users can catch that exception and handle it gracefully.