Avoid breaking Calculator when avalara_response
is not a hash
#177
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I ran on a scenario where the
avalara_response
would not benil
but not be a Hash either when the request failed - causing a crypticundefined method :each for nil class
up the stack. It was related to imported Orders that tried to calculate tax with Avalara.In any case, this is just a naive fix, but it should hopefully save some headache from people that encounter something similar in the future.