binance_client 1.2.0 → 1.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 65dba4f920f7c9e017d74cee2c972ae54af6f731faa17c6eb15c9602061e0bb7
-  data.tar.gz: 0aa2e07fac3321d91513d0ab3904e80f09351b538507d7b915cf20145166f13f
+  metadata.gz: 52c8b1596a4976bc9b6e2743fad40d6e33d050f6a614bcb550128ce29bb97d00
+  data.tar.gz: 2cb12b4ad491d438303a745e357793f4c2d9df97d66c05fd59226f2649e7b492
 SHA512:
-  metadata.gz: e72bc48d33af094253cbbe395f9bf8f6d67343a7bcc8cf912e69740e4733c4161f7a1d06fc4755f1ff236f214b8026c1f896b360b99204e9338b18c02e95b906
-  data.tar.gz: 43f1d01d8a1ac0ab5fd540f13933e4d5cd17d34f063ab1dc924372a0a94e74599c4672fbeb411e6378c97f86182eb61a46a8ee3285c1838f98ce11d17b3706cd
+  metadata.gz: cd519eeaff647220d99d6abea75054cc1eae2fd2dea9f6733d44afb4c40977957aeb74e8720bda35f5d159fff28d4092a0bb1c6fcddc3995bdc8bb84d5a4ccda
+  data.tar.gz: 0d4570d268372084d100619469064d6ae5f364e63b99d6c0063f6bb4b68f1b6dad84a94bccd15d1308361a7bfe72371791e2a27f5f3a97465217f200f076a931

data/CHANGELOG.md

@@ -4,6 +4,10 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.3.0] - 2021-11-29
+### Added
+- Add proxy support
+
 ## [1.2.0] - 2021-11-26
 ### Added
 - Allow easy access to the `used_weight` header in a response by calling `#used_weight(interval)`

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    binance_client (1.2.0)
+    binance_client (1.3.0)
       activesupport
       api_client_base (~> 1.11)
       typhoeus

data/README.md

@@ -46,15 +46,15 @@ The default representation of response data is a JSON hash
 You can set a hook to do application-specific things per request. This is useful when monitoring the rate limits:
 
 ```ruby
-BinanceClient.after_request = DoSomethingAfterBinanceRequest
+BinanceClient.configuration.after_response = DoSomethingAfterBinanceResponse
 ```
 
 What you assign can be a proc -- it just needs to respond to `call` and accept the `BinanceClient` response object:
 
 ```ruby
-class DoSomethingAfterBinanceRequest
+class DoSomethingAfterBinanceResponse
 
-  def self.call(response)
+  def self.call(request, response)
     one_minute_weight = response.used_weight("1m")
     if one_minute_weight > 1200
       Rails.logger.info "Looks like we've hit the request limit!"

data/lib/binance_client/client.rb

@@ -12,11 +12,12 @@ module BinanceClient
     attribute :host
     attribute :api_key
     attribute :api_secret
+    attribute :proxy
 
     private
 
     def default_opts
-      {host: host, api_key: api_key, api_secret: api_secret}
+      {host: host, api_key: api_key, api_secret: api_secret, proxy: proxy}
     end
   end
 end

data/lib/binance_client/version.rb

@@ -1,3 +1,3 @@
 module BinanceClient
-  VERSION = "1.2.0"
+  VERSION = "1.3.0"
 end

data/lib/binance_client.rb

@@ -39,5 +39,6 @@ module BinanceClient
     has :host, classes: String, default: DEFAULT_HOST
     has :api_key, classes: String
     has :api_secret, classes: String
+    has :proxy
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: binance_client
 version: !ruby/object:Gem::Version
-  version: 1.2.0
+  version: 1.3.0
 platform: ruby
 authors:
 - AJ Villalobos
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-11-26 00:00:00.000000000 Z
+date: 2021-11-29 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: api_client_base