Skip to content

Latest commit

 

History

History
60 lines (42 loc) · 1.75 KB

CHANGELOG.md

File metadata and controls

60 lines (42 loc) · 1.75 KB

0.3.0 / April 12, 2013

  • api_login -> environment_key
  • api_secret -> access_secret
  • spreedlycore.com -> core.spreedly.com
  • Fixed an issue with multiple errors in a PaymentMethod

0.2.2 / October 18, 2012

  • Increased the timeout when talking to gateways.

0.2.1 / October 18, 2012

  • Fixed issue with create payment method API call.

0.2.0 / September 24, 2012

  • Support all 3.x versions of ActiveSupport
  • Support all 0.x versions of HTTParty

0.1.2 / February 29, 2012

  • Fix bug where a response with no body could raise a NoMethodError on NilClass

0.1.1 / February 29, 2012

  • Update Rakefile to include bundler tasks for building and releasing the gem

0.1.0 / February 29, 2012

  • Allow configuring via a set of key/values or with the traditional 3 arguments. For example: SpreedlyCore.configure :login => 'login', :secret => 'secret', :token => 'token' or SpreeclyCore.configure 'login', 'secret', 'token'

  • Handle exceptional cases better. There are 2 types of exceptions which can be raised by the library:

    1. SpreedlyCore::TimeOutError A TimeOutError is raised if communication with SpreedlyCore takes longer than 10 seconds
    2. SpreedlyCore::InvalidResponse An InvalidResponse is raised when the response code is unexpected (I.E. we expect a HTTP response code of 200 bunt instead got a 500) or if the response does not contain an expected attribute. For example the response from retaining a payment method should contain an XML attribute of "transaction". If this is not found (for example a HTTP response 404 or 500 is returned), then an InvalidResponse is raised

    Both TimeOutError and InvalidResponse subclass SpreedlyCore::Error.