Clearing up the documentation with practical API examples #468

Open
sidneydobber opened this Issue Jun 4, 2014 · 0 comments

2 participants

@sidneydobber

I have a problem, but I don't know if it's an issue though. I have a relational model which has 'POST', 'PUT' and 'DELETE' functionality. It also has a relation pointing to it that is used by another part of the application. The problem is that the 'POST' reverts to a 'PUT' because the 'id' attribute contains a collection that get's added by the other model. When I remove the reverse relation all works fine.

UPDATE TO ORIGINAL QUESTION:
The problem was solved, but after a little dialogue we stated that the documentation could be more practical and clear. As an example the implementation of a specific API and not just manually created collections, because this was where things got unclear for me. I will try and setup up a JSFiddle and a list with issues that aren't clear from the docs.

@sidneydobber sidneydobber changed the title from Having two identical 'reverseRelation keys' messes up 'RESTful' methods. to Adding an unused relation makes the POST revert to a PUT Jun 4, 2014
@sidneydobber sidneydobber changed the title from Adding an unused relation makes the POST revert to a PUT to Adding an unused relation fills the id attribute with a collection Jun 4, 2014
@sidneydobber sidneydobber changed the title from Adding an unused relation fills the id attribute with a collection to Adding an unused relation, fills the id attribute with a collection Jun 4, 2014
@sidneydobber sidneydobber changed the title from Adding an unused relation, fills the id attribute with a collection to Clearing up the documentation with practical API examples Jun 17, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment