Anatomy of an Observable Rx.JS

[haffani]

Suggestions:

• Observable described as nothing more than an object with forEach function, this function will accept an observer which is in his role nothing more than an object with 3 function onNext, onError Completed.

we can make an implementation.

• We can discuss how Iterator and Observer patterns are symmetrical, -> In Ob. pattern, the producer iterate you by calling onNext, onError or on Completed. -> In Iter. pattern, it's the consumer who iterate you.

How Observables helps on the standardization of a lot of push APIs such as DOM events, service workers, node streams, jquery events...

Questions:

• How to catch/detect memory leaks and async problems caused by the unhooked subscriptions in my Angular application?

• I'm unhooking my subscriptions in angular "ngDestroy" life cycle method, it works but what are the best practices?

• When exactly BehaviorSubject is useful?

[chihab]

Hi @liffanu, thank you for your interest.

Are these a meetup proposal or questions for us or Ben Lesh?

[haffani]

Hello @chihab, Yes, i guess.. maybe we can talk about those topics about reactive programming.

[chihab]

@liffanu hopefully Ben will answer some of your questions. Otherwise we can plan an RxJS remote workshop. Meanwhile you can take a look at an implementation of RxJS principles here https://github.com/chihab/rabatjs-rxjs (code is also on codesandbox) https://codesandbox.io/s/github/chihab/rabatjs-rxjs