My sense of restangular is that it was pretty useful if your use case matched the design of restangular directly. Mine didn't, and it was just as much work to get restangular to do what I wanted as to build some custom abstraction on top of $http. So I went with the latter plan.
It is also worth looking at angular-data - http://angular-data.pseudobry.com/ I haven't used it myself, (my custom layer is working great, so I don't really want / need to refactor to use a different library), but it looks promising. e On Thu, Oct 16, 2014 at 7:29 AM, Anton Trapp <[email protected]> wrote: > Hi Sander! > > I use the same approach on most Rails stuff I use :) > > From what I read it sounds too complicated, took a look on the code. 1 > file with > 1k lines. Answers my question :D > > I think I use $resource in the simple cases and go with $http whenever the > hack to get $resource delivering what I want gets to big... > > Tnx!!! > > -- > You received this message because you are subscribed to the Google Groups > "AngularJS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
