v0.2.2
We don't like errors, but they happen anyways.
Summary
This release focuses on simplifying the handling of errors by making the interface more consistent.
Breaking changes
- Removed message field from
ExecResponse
, the data that would be stored there is now stored in stdout, stderr, and output on responses where message would have beenSome
. Now the user will not have to check for the existence of message, they can just use any of the already guaranteed fields on the response.
Additions
- HTTP status code is now included in non 200 response error messages.
- Language and version are now always passed back with the response, previously they would be an empty string on non 200 responses.
- Updated examples with cleaner, more accurate error handling.
Bugfixes
is_ok
andis_err
onExecResult
andExecResponse
now properly determine status using the process status code rather than stdout, and stderr.
Full Changelog: v0.2.1...v0.2.2