wepay / ruby-sdk Goto Github PK

Hello,

I just wanted to let you know of an error I was receiving when calling the oauth2_authorize_url method that is part of the Client class. This might be due to having certain versions of certain files, but if I made the following changes:

Things seemed to go back to normal for this call. I got the idea from this page:

and the reason I'm giving you a screenshot instead of a link to that page is because I think the site is actually down now, but google let me view a cached copy of the page that didn't have any styling and some characters missing. Here is THAT link. Hope this helps. Thanks for the gem.

Hi Guys,

Right now wepay-rails uses HTTParty for communications with the wepay api. I'd like to change that and use your SDK instead. We are starting a major testing effort on the wepay-rails gem and I was hoping that you guys could write some around your SDK that can call your service in a real way vs. stubbing out some responses. This would help us to ensure that our code is good as well.

Thanks in advance,

Adam (wepay-rails)

Is there any way to configure and not log to $stdout? or thoughts? I don't like running rspec tests and seeing the net http calls.

I thought of $stdout.stub(:write) for my tests but it wouldn't work well with pry :)

Thanks!

Hi,

Using rails 4.1.0, wepay 0.0.3

ONLY when I call a cancel subscription call, i am getting this error:

JSON::ParserError:
A JSON text must at least contain two octets!

When i do a raise on the response.body object (raise response.body.inspect) I get this:

"{"subscription_plan_id":1425787008}"

The JSON looks ok. Also, when I do:

JSON.parse("{"subscription_plan_id":1425787008}")

It parses just fine? I am totally stumped as to why I'm getting this error. Anyone else having this problem?

'gem unpack wepay' still shows the code which is old and does not contain the recent fixes.
Please update wepay RubyGems with the updated code

Is there any reason this can't be added as a gem?

Currently authorization header is added using
call.add_field('Authorization: Bearer', access_token);

This gives error sometimes with message suggesting authorization header should be of type Bearer when the header is not added correctly to the HTTP request

Using header name as 'Authorization' and passing the value 'Bearer <access_token>' works for me as following:-
call.add_field('Authorization', "Bearer #{access_token}");