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
With the current approach, all requests return only the response body, that is, a JSON that is converted into a hash. That means it's not possible to know information about rate limiting, cache and more.
Would there be interest to instead return the HTTP object and let the client call response.body, instead of prohibiting the client from accessing anything other than the HTTP body?
The text was updated successfully, but these errors were encountered:
With the current approach, all requests return only the response body, that is, a JSON that is converted into a hash. That means it's not possible to know information about rate limiting, cache and more.
Here's an example: https://github.com/Jakenberg/binance-ruby/blob/master/lib/binance/api/account.rb#L26-L28
Would there be interest to instead return the HTTP object and let the client call
response.body
, instead of prohibiting the client from accessing anything other than the HTTP body?The text was updated successfully, but these errors were encountered: