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
{{ message }}
This repository has been archived by the owner on Sep 15, 2021. It is now read-only.
I've searched long and hard, but couldn't find much information about why ListPathObserver got to be deprecated (besides that it's has been removed from observe-js), or indeed what's the recommended alternative.
I guess the use cases for it remain as valid as they seemed to be. For example, computed sublists based on values (deeply) inside their members.
Do you see that as a bad practice? Outside the scope of the package? Or is it covered otherwise?
cheers
f
The text was updated successfully, but these errors were encountered:
fabiosimeoni
changed the title
Plan B for ListPathObserver?
Plan B for ListPathObserver?
Apr 14, 2015
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've searched long and hard, but couldn't find much information about why
ListPathObserver
got to be deprecated (besides that it's has been removed fromobserve-js
), or indeed what's the recommended alternative.I guess the use cases for it remain as valid as they seemed to be. For example, computed sublists based on values (deeply) inside their members.
Do you see that as a bad practice? Outside the scope of the package? Or is it covered otherwise?
cheers
f
The text was updated successfully, but these errors were encountered: