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
While the docs state that legacy stores created with DstoreAdapter will be observable if the originating dstore instance is trackable (and I've seen that in action), the reverse does not appear to be the case. In fact, there seems to be no reference to observe anywhere in StoreAdapter.
Given that the observation models between dojo/store and dstore are quite different (to the point where dojo/store's observe is tucked away on query results whereas track is exposed at the top level), is this something that wasn't considered realistic to implement? It seems like it'd be quite an impediment to the adapter being useful for migration purposes.
While the docs state that legacy stores created with DstoreAdapter will be observable if the originating dstore instance is trackable (and I've seen that in action), the reverse does not appear to be the case. In fact, there seems to be no reference to
observe
anywhere in StoreAdapter.Given that the observation models between dojo/store and dstore are quite different (to the point where dojo/store's
observe
is tucked away on query results whereastrack
is exposed at the top level), is this something that wasn't considered realistic to implement? It seems like it'd be quite an impediment to the adapter being useful for migration purposes.Example page (in which tracking doesn't work):
The text was updated successfully, but these errors were encountered: