-
Notifications
You must be signed in to change notification settings - Fork 416
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
Malformed params creation on POST when params added to body #67
Comments
Damn! I needed to set the "consume" value to 'application/json'! I'll close the issue but leave that here just in case somebody googles it, if that's ok. |
I've a similar issue but
Here is my code. What am I missing?
Edit: I've switched from |
Hello,
Thanks a lot for that gem, it's great! I have a small issue however, and cannot figure out what is going on; I have the following spec code to test a sessions controller:
it works as expected, however the params arrive to my app in this form:
As you can see, I end up with params in a weird form, i.e
which makes me unable to extract them from the params to perform my sign up mechanism - what is weird is that with the generated documentation, when using the "try it" feature, the params are actually sent properly. Would you have an idea about how I could get this sorted? Thanks a lot in advance!!
This is how the params are formed when I use the "try it" feature:
As you can see, it's all hunky dory in this case :\
The text was updated successfully, but these errors were encountered: