Fixed
Status Update
Comments
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #2
Yigit, do you have time to fix it?
reemission of the same liveData is racy
reemission of the same liveData is racy
il...@google.com <il...@google.com> #3
yea i'll take it.
na...@google.com <na...@google.com> #4
Thanks for the detailed analysis. This may not be an issue anymore since we've started using Main.immediate there but I' not sure; I'll try to create a test case.
Description
Following conversation here:https://kotlinlang.slack.com/archives/CJLTWPH7S/p1638968657294300
We're working on a "compose new message" screen, whose recipients box might be prefilled. We want to pass these optional recipients (e.g. contact ids) to this screen, ideally with the same format used by our server: example.com/newmessage?to=contact1&to=contact2 , using navigation library routes.
Repeated query params is a common way to pass arrays. It would be nice if navigation routes supported this pattern too. There is also a less common, but more explicit pattern of adding square brackets, e.g. to[]=me&to[]=you - this might be considered as well.