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
I'd like to open a discussion whether it would be useful to add oldValue parameters to Update and Remove operations or I'm just missing something useful?
E.g. my current use case is this: I'm using ReactiveArray to manage annotations displayed in MKMapView. On my viewModel I have an array which changes based on items that came from API. So in cases when the array changes I'd like to update/remove appropriate annotations which currently seems to be impossible or complicated.
I think that adding a simple argument oldValue to those operations wouldn't be that complicated and would solve those cases effectively.
Other opinions? :-)
The text was updated successfully, but these errors were encountered:
Hi,
I'd like to open a discussion whether it would be useful to add
oldValue
parameters toUpdate
andRemove
operations or I'm just missing something useful?E.g. my current use case is this: I'm using
ReactiveArray
to manage annotations displayed inMKMapView
. On my viewModel I have an array which changes based on items that came from API. So in cases when the array changes I'd like to update/remove appropriate annotations which currently seems to be impossible or complicated.I think that adding a simple argument
oldValue
to those operations wouldn't be that complicated and would solve those cases effectively.Other opinions? :-)
The text was updated successfully, but these errors were encountered: