Working with a restangular sub resource

Question

I have a child resource which will have full set of methods associated with it. I am starting to implement the create (i have the back end working). Essentially I want to be able to work with this structure

http://127.0.0.1:8000/rest/parent_resource/<parent_id>/child_resource/

Where is an integer field identifying a parent object. For example:

http://127.0.0.1:8000/rest/parent_resource/87/child_resource/

For security reasons, I don't want to expose the collection as a whole to the end users. So therefore obj.child_resource = [{blah}] is not an approach I am considering. The parent_resource / collection is owned by one user, with contributions (create) to the collection from other users who can update/delete their contribution to a collection.

I am lost as to how to set this up with restangular. I am thinking about messing about with this, but I don't think appending my identifier to the URI is the right way forward:

app.factory('ParentResource', function (Restangular) {
    return {
          getList: function() {
            return Restangular.all('rest/parent_resource').getList()
          }
          , get: _.memoize(
            function (id) {
                return Restangular.one('rest/parent_resource', id).get()
          })
          , createChild: function(parentId, field_1, field_2) {

            var newChild = {
                "field_1": field_1
                , "field_2": field_2
            }

            return Restangular.all('rest/parent_resource/' + parentId + '/childResource').post(newChild )
        }
    }
})

Usage would be something like

ParentResource.get(87).then(function(parentObj){
     parentObj.createChild(1,2)
})

One sidenote: 'I don't want to expose the collection as a whole to the end users' - it is called 'security through obscurity'. If collection id is such a sensitive number - consider replacing it with random hash (associated with collection id on your backend). Otherwise collection id's could be iterated through to find existing ids — borisano
– borisano, Commented Aug 25, 2015 at 15:32

akaphenom · Accepted Answer · 2014-01-14 21:51:56Z

1

I am going to investigate this solution:

 return Restangular.one('rest/parent_resource', parentId).all('child_resource').post(newChild)

in this context:

app.factory('ParentResource', function (Restangular) {
    return {
          getList: function() {
            return Restangular.all('rest/parent_resource').getList()
          }
          , get: _.memoize(
            function (id) {
                return Restangular.one('rest/parent_resource', id).get()
          })
          , createChild: function(parentId, field_1, field_2) {

            var newChild = {
                "field_1": field_1
                , "field_2": field_2
            }

              return Restangular.one('rest/parent_resource', parentId).all('child_resource').post(newChild)
        }
    }
})

answered Jan 14, 2014 at 21:51

akaphenom

6,89611 gold badges62 silver badges113 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

akaphenom Over a year ago

This works - I don't know if it is the preferred solution, nor have I spent anytime diagnosing side effects - at this stage I am getting my app up and running will optimize/productionalize later

Collectives™ on Stack Overflow

Working with a restangular sub resource

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related