Friday, July 24, 2015

Re: [Rails] Making rails-api (rails 4.0.2/9) work with strong parameters.

Your payload looks like a string, is permit something you can call on a string object?



> On Jul 24, 2015, at 9:31 PM, Donald Ziesig <donald@ziesig.org> wrote:
>
> Hi All!
>
> I have been trying just about everything I can find on the web to make rails-api work with strong_parameters but no matter what I do, I get the following error:
>
> NoMethodError (undefined method `permit' for "{email: xxx@xxx.org, password: xxxxxxxxx}":String):
>
> All of the answers I have found give ways to add StrongParameters to ApplicationController::Api, but none of them change the resulting error. Debug printouts show that the recommended changes are being executed. I generated a test app using rails without -api and it works fine, but is much bigger due to all of the non-api cruft.
>
> I am using both rails 4.0.2 and 4.0.9 (can't use higher versions due to some old but necessary gems).
>
> Any help would be appreciated.
>
> Thanks,
>
> Don Ziesig
>
> --
> You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
> To post to this group, send email to rubyonrails-talk@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/55B2E6FF.9060607%40ziesig.org.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/1A9F420C-956D-4C41-B316-A94E92C9CAE3%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment