Skip Menu |

This queue is for tickets about the Business-Tax-Avalara CPAN distribution.

Report information
The Basics
Id: 86860
Status: resolved
Priority: 0/
Queue: Business-Tax-Avalara

People
Owner: Nobody in particular
Requestors: jterry [...] bluehost.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Authentication and timeout errors
Date: Thu, 11 Jul 2013 10:07:08 -0600
To: bug-Business-Tax-Avalara [...] rt.cpan.org
From: Jason Terry <jterry [...] bluehost.com>
When Business::Tax::Avalara gets any kind of error it simply logs it and returns nothing. This doesn't give the developer much control over trying to report or handle specific error types. In the case of a timeout it's not a huge deal since you have no data anyway. However if you submit invalid credentials an actual "400 Bad Request" which includes well formed JSON is logged, but not passed back. It would be nice if well formed JSON errors like that were actually sent back rather then simply logged and discarded. Thanks -Jason
On Thu Jul 11 12:07:31 2013, jterry@bluehost.com wrote: Show quoted text
> When Business::Tax::Avalara gets any kind of error it simply logs it and > returns nothing. > > This doesn't give the developer much control over trying to report or > handle specific error types. > > In the case of a timeout it's not a huge deal since you have no data > anyway. However if you submit invalid credentials an actual "400 Bad > Request" which includes well formed JSON is logged, but not passed back. > > It would be nice if well formed JSON errors like that were actually sent > back rather then simply logged and discarded. > > Thanks > -Jason
This is a great idea. I'm probably not going to get to it soon, but patches are welcome and I'll take the time to integrate and release if someone sends me one!
Fixed in version 1.1.0, now I return the response on failure, not undef.