-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
"not opened for reading" on ams > 0.9.3 #1038
Comments
Hey @johnhamelink, first of all I'm really glad to hear the you are building cutting-edge API's! 😄 |
Cheers! We're using 0.9.3 right now to get started, but we'll want to switch over to 0.10 asap so we don't need to rewrite too much client side code :) Let me know if there's anything I can do to help! |
I have the same error with rails 4.2 and AMS Hard to say where is exactly this problem, as I have similar serialisation logic and this error appears only during rendering particular models.
|
I saw
|
For my case it seems, like it also related to #963. But I'm using mongoid, so relation probably handles in a different way. Renaming |
Also, grape-ams doesn't work with the current version of ams |
@bf4 seems like you're always a couple days ahead of me! I am getting the same error as @yokree with the same versions just FYI. Grape support would be awesome. |
I think this has been addressed and may be closed? |
@bf4 yep! Closing issue. |
Hey there,
I'm working on a new API project where I'm using AMS with Grape and Swagger-UI. I wanted to use the 0.10.0 release candidates so I could utilize JSON-API in full while building my API. However in both
0.10.0.rc1
,0.10.0.rc2
, and git master I get the following error when trying to serialize (JSON output from Swagger UI):Stack Trace:
My
Gemfile.lock
:Example code which causes this error:
app/api/fap/v1/sessions/sso.rb
:app/api/fap/v1/defaults.rb
:The text was updated successfully, but these errors were encountered: