You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
sidneydobber
changed the title
Having two identical 'reverseRelation keys' messes up 'RESTful' methods.
Adding an unused relation makes the POST revert to a PUT
Jun 4, 2014
sidneydobber
changed the title
Adding an unused relation makes the POST revert to a PUT
Adding an unused relation fills the id attribute with a collection
Jun 4, 2014
sidneydobber
changed the title
Adding an unused relation fills the id attribute with a collection
Adding an unused relation, fills the id attribute with a collection
Jun 4, 2014
sidneydobber
changed the title
Adding an unused relation, fills the id attribute with a collection
Clearing up the documentation with practical API examples
Jun 17, 2014
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.
The text was updated successfully, but these errors were encountered: