Hi Sander, Thanks for your assistance and clarifications. Will do as you advised and store down somewhere instead, np. Best regards,
Richard. On 29 Oct 2014, at 14:06, Sander Elias <[email protected]> wrote: > Hi Richard, > > You know the URL when you call out for the $resource, don't you? It might be > a good idea to store it then, and keep it around for later on. > My first idea is however, when configuring the resource in the first place, > why don't you add an `deleteAll` method to it? That's the place > that's meant to do stuff like you are asking. > > It is indeed not easy to get the URL back out from the resource, and I'm a > bit hesitant on enabling this, because it goes against the hair of the fur. > > Regards > Sander > > > > > > -- > 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.
