You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When calling some methods from the SDK, like Client#exchange_rates_get_specific_rate, there are some edge cases - in particular, the test API Key has no access to the "specific exchange rate" endpoint, so it gets a 403.
But the method still tries to parse the date before returning the object, which results in an obscure "nil can't be parsed" sort of error.
Many such details exist.
Does the SDK intend to pass the message object with the error?
The text was updated successfully, but these errors were encountered:
I think SDK should throw an exception in this case with error message received from the API, such an exception object will unwind a call stack to the user code or beyond.
Can you confirm that such behavior don't exists in the master branch?
When calling some methods from the SDK, like
Client#exchange_rates_get_specific_rate
, there are some edge cases - in particular, the test API Key has no access to the "specific exchange rate" endpoint, so it gets a 403.But the method still tries to parse the date before returning the object, which results in an obscure "nil can't be parsed" sort of error.
Many such details exist.
Does the SDK intend to pass the message object with the error?
The text was updated successfully, but these errors were encountered: