Issue is a bit obscure, if a token is sent to the 'post' method but the
path sent already includes a '?', an error was thrown. This fix places
either a '?' or a '&' before the token as appropriate.
Both post and get requests assumed that the response from the server
would include a "data" field, which is not the case. Moved handling of
the data element back into the invoice and pairing methods.
bumped gem version to 2.4.1
The library now uses the crpytographically secure API.
more tests plus CLI enhancements
Library no longer supporting ruby 1.9.x
1.9.x will be deprecated in February of 2015, so there is little
incentive to write our new library to support it. 1.9.x users should
still be able to use V1 of the API.
This commit adds some changes, such as named arguments, that are
incompatible with 1.9.x.
Add Rake tasks to clear limiters
When many integration tests are run in a short period, the local bitpay server
will refuse to create new keys due to the rate limiting function. This
rake task clears the ratelimiters database.
