-
Notifications
You must be signed in to change notification settings - Fork 27.4k
feat(ngInclude): emit $includeContentError when HTTP request fails #5825
Conversation
lgtm |
wouldn't it make sense to have |
Also, do we really want to report an error even if |
@shahata re: the onerror thing, I'm not totally opposed to it, but I think it should wait until people ask for it at the very earliest. Even this event is probably a bit much, but it's been asked for a bit. As for emitting the error even if it wasn't for the same change counter, I'm not sure it really makes a huge difference, because in practice people aren't changing the expression and running a digest 50 times before the response arrives. But it's a small change to make it work like that, so I guess that's fine. |
Thanks cait. Looking forward to this merge |
Yeah, this should be pretty trivial, @petebacondarwin or @matsko can you give this a quick review and see if @shahata's concern needs to be addressed? I'll talk to Igor about merging this on Thursday |
@caitp I agree with you that we should wait on adding |
Other than that LGTM |
yeah, we should emit the error only if the error is for the current request |
This adds a scope event notification when a template fails to load. This can have performance implications, and unfortunately cannot at this moment be terminated with preventDefault(). But it's nice to be notified when problems occur! Closes angular#5803
PTAL, I think that should be everything |
Landed as e4419da. |
This adds a scope event notification when a template fails to load.
This can have performance implications, and unfortunately cannot at this moment be terminated with preventDefault(). But it's nice to be notified when problems occur!
Closes #5803