Fixed
Status Update
No update yet.
Comments
se...@google.com
Also, it would be great to return Observable, cause Flowable has some overhead.
se...@google.com
We are going to add Single for queries (and Maybe) but for @insert, @Update and @Delete it is a bit more tricky because we would be reading those values when the computable runs, in which case developer may change them by mistake. We've not decided whether we want to take that risk or not. (We could copy but that would be additional hidden load, especially if the input is a long list).
#2, flowable can easily turn into an observable, would you like to escalate on why you think the overhead is a problem?
#2, flowable can easily turn into an observable, would you like to escalate on why you think the overhead is a problem?
yb...@google.com
Cool for Single/Maybe for queries :)
For @insert, @Update and @Delete I personally would like to have the possibility to have Single/Maybe... because I will 100% of the time wrap the call into a Single to make it asynchronous and have the possibility to chain other actions with it. I understand that copying entries will take additional resources but in that case we'll have the possibility to not use the RX return type.
That my opinion ^^
Thanks !
For @insert, @Update and @Delete I personally would like to have the possibility to have Single/Maybe... because I will 100% of the time wrap the call into a Single to make it asynchronous and have the possibility to chain other actions with it. I understand that copying entries will take additional resources but in that case we'll have the possibility to not use the RX return type.
That my opinion ^^
Thanks !
se...@google.com
Shouldn't this be typed as a feature request?
ch...@beyls.net
ne...@gmail.com
This issue is half year old and it's still not implemented. Without this the library is unusable.
m....@gmail.com
+1
yb...@google.com
yb...@google.com
ap...@google.com
+1 Here as well. I would like Completable support.
yb...@google.com
yb...@google.com
+1 i think Completable support is necessary
yb...@google.com
+1 for Completable support as well
yb...@google.com
+1 for completable - just missed it on the fly while coding
ap...@google.com
+1 for Completable support as well
Description
repro steps from the developer:
launch the app on a device, press the button to update the counters. Then after you use "force gc" from android monitor, the second counter will stop updating
Looks like because nothing keeps a reference to the AlwaysOnLifecycle or the LiveData, both end up being GC'ed. Before it was a single instance so it didn't get GC'ed.
We probably need to keep AlwaysOnLifecycle in memory as long as it has an observer.