Thinking about stream.where, are you repeating yourself by having the same predicate twice?
Partition would enable using only a single predicate and returning the two different streams, thus not violating DRY.
Not saying we shouldn't have partition, but it would just be much nicer once destructuring lands (eventually).
In the meantime, 2 wheres are not that bad
Hello. I have made pagination using by rxdart. Which Subject choose?
@kimjisung78 that's a pretty vague question, are you asking what the different Subjects do?
I'm sorry to leave you with such a difficult question. I can’t understand the difference between PublishSubject and BehaviorSubject. And I don’t know “Which one is better if I want to make pagination?”
@kimjisung78 they both allow multiple subscribers, but the difference is that when subscribing to a BehaviorSubject, then the last added event will be replayed immediately.
Hello everyone, I'm fairly new to rxdart. I have heard about doOnDone. How would I trigger the done on an subject?
@schmidtfx you need to call close()
Hi, is there guide when to use operator and which operator to use for rxdart? Thanks
RxDart has much in common with RxJs, or other Rx implementations, we don't have an equivalent in RxDart
@frankpepermans thanks for creating powerful library
Hi! Just made the 22_to_23 switch
so far everything seemed to work fine, but there's one error that I get now:
.shareValue() doesn't exist anymore
Since it's an extension I need to import rxdart for it to exist.
Got it :)
Great job! Thanks for also providing the codemod
One suggestion though: add the .seeded() factory constructor to the codemod
I had to replace all of this manually
great :) we're on 0.24.1 meanwhile, but that shouldn't be too big a change
Hello, I would like to know how do I execute a function when something is emitted (sink / add) in the controller, I know doOnData but it only works if someone is listening to the stream.
I have a common usage where I want a ValueStream which doesn't shut down when it no longer has listeners. You could imagine that you have a global ValueStream for a Firestore document, and you never want this stream to close due to changes in the number of subscribers, e.g. The workaround I have right now is to register a no-op listener upon creation of the ValueStream, which then "tricks" the stream into thinking it always has a listener. Is there a better pattern I could adopt for this?
@rafaelcorbellini-egsys Streams by design only become active after an initial subscription, doOnX would then be a good choice like you mentioned.