Yeah, I'd put a .catch on the end of that promise chain to see what the error is. My hypothesis is that Order.query is failing, but it is hard to say why. The problem with promises (and asyncs in general) is that unless you explicitly look for errors, you'll miss them.
Which is why I put an .catch (err) -> console.log err at least on all my promise chains. Or next err if we are on the node side. e On May 26, 2014 1:57 PM, "Steve Jackson" <[email protected]> wrote: > Not sure without running it to see what it does for me, exactly, but at > first glance I see that there isn't any protection around having objects > that are null. Anytime I have more than 2 dots after a variable I check for > null before referencing properties... > > Is it possible that you have a null reference happening? Doors anything > show up in the browser's console? > > Steve > > -- > 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.
