You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Automatically unsubscribe once the object is destroyed -- no more need for removeObserver directly
Probably not necessary, and this would require injecting code into willDestroy -- not great
Could unsubscribe use this internally?
Turns out the safe answer is "no" -- I saw something earlier today saying that an observer should not create a subscription, and refactoring to use fromPropertyChange in the subscribe decorator would require that.
Idea: turn a stream of property changes into an Observable.
removeObserver
directlysubscribe
use this internally?The text was updated successfully, but these errors were encountered: