Verified
Status Update
Comments
il...@google.com <il...@google.com> #2
Also, it would be great to return Observable, cause Flowable has some overhead.
ga...@google.com <ga...@google.com> #3
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?
ap...@google.com <ap...@google.com> #4
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 !
ap...@google.com <ap...@google.com> #5
Shouldn't this be typed as a feature request?
ap...@google.com <ap...@google.com> #6
jb...@google.com <jb...@google.com> #7
This issue is half year old and it's still not implemented. Without this the library is unusable.
Description
Component used: activity-compose -
PredictiveBackHandler
Right now, when getting the progress events, you can tell the
touchX
andtouchY
and the progress, but you’d need to manually track the velocity to understand the velocity with which a gesture is performed.I’d like this velocity to be able to use
animateDecay
, oranimateTo()
onAnimatable
, to be able to smoothly finish the animation from where it left off. To do this, I’ve addedVelocityTracker
, but the BackEvent doesn’t containuptimeMillis
, leading me to useSystem.currentTimeMillis
, which could be inaccurate if an event comes in a different order.