-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resp.join #1
Comments
I assume you are using cuba and/or cuba-api cuba uses its own Cuba::Response class which is not Rack::Response - that might be the confusion. a call to Cuba.call will return so I am not sure where the Rack::Response comes from. the Cuba.call will execute #finish on the Response (whatever Response class you are using) which returns the above array if you give me more inside what you are doing I might be able to help further |
@mkristian thank you for the response. I'm using Cuba, which is why I was confused I didn't get the same result as you. Here are the tests https://github.com/cj/cuba-tools/blob/master/test/tools/widget_test.rb Thank you again! |
the Cuba::Tools::Widget::Responder uses Rack::Response which will be Cuba usually uses Cuba::Response instead of Rack::Response which uses a so either you use Cuba::Response as well or at least |
ah thank you, that makes perfect sense now. one other thing when passing in the |
'ello. I quick question, hopefully you can answer it as it's driving me nuts. I noticed you were doing this
cuba-api/spec/current_user_spec.rb
Line 43 in 64fadee
resp.join
when I try that in my own tests I getNoMethodError: undefined method 'join' for #<Rack::Response:0x00000002e63988>
so end up having to dobody = resp.send('body').join
. Any idea on what I'm missing?The text was updated successfully, but these errors were encountered: