{"push_id":724463235,"size":1,"distinct_size":1,"ref":"refs/heads/Reversals","head":"ecf3eeca33dfcce5632bc16b0cc25ef76661c259","before":"651f5569f9e80659f696afb71412a27d53cb9249","commits":[{"sha":"ecf3eeca33dfcce5632bc16b0cc25ef76661c259","author":{"email":"2417c754f4155f87f176ff78f3d176f87ae2bc05@gmail.com","name":"Dan Schmidt"},"message":"Support Transfer Reversals (#20)\n\nAdds support for reversing existing transfers via a new create_reversal method. This method accepts three arguments:\n\n- (Required) The transfer ID - any stringifiable value\n- (Optional) Reversal data - a hashref defaulting to {}\n- (Optional) Options - a hashref defaulting to {}. Right now the only valid key is 'headers', which is passed verbatim to the LWP::UserAgent as request headers.\n\nThe method signature ($id, $data = {}, $opts = {}) is meant as a template for all methods that act on a single, existing object. Right now, WS::Stripe uses a mix of positional and named parameters that is not consistent and requires looking back at the documentation. We should unify these signatures to promote understanding. For operations involving new objects, I'd propose the very-similar signature ($data, $opts = {}).","distinct":true,"url":"https://api.github.com/repos/Crowdtilt/WebService-Stripe/commits/ecf3eeca33dfcce5632bc16b0cc25ef76661c259"}]}