-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Updating documentation with the default expected API responses. #3257
Comments
I think @bmac would be able to point you in the right direction here. I don't know if he has it in his guides updates. |
This info looks great @stefek99. I don't think it exits in any one place in the guides. The table on the the-rest-adapter guide is the closest thing that I know of, however it doesn't have nearly this level of information. |
Thank you for your input. One thing that I've discovered after 3 weeks of deep dive into Ember and Ember CLI and Ember Data - plenty of jsfiddle / jsbin examples are not working - people linking to 'latest' versions - and in general it is not a good idea as described here: http://blog.jquery.com/2014/07/03/dont-use-jquery-latest-js/ On the same note - many of the blogpost / StackOverflow answers are no longer accurate. (feel free to close this issue, I just wanted to let you know about the table with expected responses) |
I started working on this in my fork. My plan is to use this twiddle for reference, and save off the pretender request/response to a Gist, with links to the JSON-API docs (for the json-api adapter and serializer). The gists would be linked to from the table in the YUI docs. Does this seem like a worthwhile approach? The hard part is presenting an example without addressing too many edge cases. There are so many ways to constructor and use endpoints, it is difficult to what would be a meaningful demonstration. |
Seems like a good idea @pete-the-pete. |
There's http://andycrum.github.io/ember-data-model-maker/, might want to enhance it. |
whoa, ember-data-model-maker is pretty slick...if supported saving or gists it could be pretty handy for reference |
I've found this question on SO greatly informative: http://stackoverflow.com/questions/14922623/what-is-the-complete-list-of-expected-json-responses-for-ds-restadapter
For instance - I didn't know (until I saw that table) that editing model creates PUT request that expects the actual object in response.
200 OK
with no data is causing parsing error202 Accepted
or204 NoContent
seems to be working fineIs that information somewhere in the docs already?
The text was updated successfully, but these errors were encountered: