With Observables you may hold an ear open as described here, and what is more with Observables you do not get anything back until you start a .subscribe or use the async pipe in the Angular markup. "ASP.NET Core 2 and Angular 5" by Valerio De Sanctis clarifies this on page 214. This same page mentions .complete() to as if it were kinda like .done() but this is going to be yet another mistake in the book. The explicit need to start listening and the ongoing listening kind of explains why you can't really have an Observable that returns void, eh?
No comments:
Post a Comment