Hi Jonathan,
It’s difficult to say anything about this, without having a reproducible example. While researching your bug, I found nothing that could explain this. If you have a a spot in your system where you can test this, can you try testing it without a $ in the resource name? Meaning, replace scope.someInstance.$resolved with something like scope.someInstance._resolved. I have a gut feeling this might help. Its a 70/30 change. So don’t get your hopes up too much. 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.
