Prerequisites
Description
When using the --output json formatting option on a request I received an http 400 error on from the vinyldns api, I discovered that it no longer prints using json formatting. Instead it prints a standard multiline, indented error message.
Steps to Reproduce
- Submit a change which will return an error to the vinyldns api
- Observe the output formatting not being respected
Expected behavior: I expect to get a json formatted error response when using the json output format, but it would apply equally to all output formats.
Actual behavior: Instead it prints a standard multiline, indented error message.
Reproduces how often: 100
Versions
Found in 0.10.1
Prerequisites
Description
When using the
--output jsonformatting option on a request I received an http 400 error on from the vinyldns api, I discovered that it no longer prints using json formatting. Instead it prints a standard multiline, indented error message.Steps to Reproduce
Expected behavior: I expect to get a json formatted error response when using the json output format, but it would apply equally to all output formats.
Actual behavior: Instead it prints a standard multiline, indented error message.
Reproduces how often: 100
Versions
Found in 0.10.1