Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Oct 15 20:35
    cartant closed #5082
  • Oct 15 20:35
    cartant commented #5082
  • Oct 15 14:03
    kwonoj closed #5083
  • Oct 15 14:03
    kwonoj commented #5083
  • Oct 15 13:32
    stasberkov commented #5082
  • Oct 15 13:00
    cartant commented #5082
  • Oct 15 12:58
    neroishero commented #5083
  • Oct 15 12:57
    neroishero commented #5083
  • Oct 15 12:57
    stasberkov commented #5082
  • Oct 15 12:47
    cartant commented #5082
  • Oct 15 12:47
    neroishero opened #5083
  • Oct 15 12:44
    stasberkov opened #5082
  • Oct 15 08:58
    cartant commented #5081
  • Oct 15 08:57

    cartant on master

    Syntax correction (#5081) (compare)

  • Oct 15 08:57
    cartant closed #5081
  • Oct 15 08:50
    VaultDeveloper opened #5081
  • Oct 15 07:58
    Edouardbozon synchronize #5006
  • Oct 15 07:58
    Edouardbozon synchronize #5008
  • Oct 15 07:57
    Edouardbozon synchronize #5009
  • Oct 15 07:20
    kwonoj synchronize #5080
Renke Grunwald
@renke
@Dorus I've played around with your second snippet, but I couldn't get it to work; source2 values come before value from source1 and come again after the values from source1. The very first snippet you sent uses shareReplay with a selector which my RxJS version (~6.5) does not seem to support .
      const foo = first$.pipe(
        publish(firstSubject$ => {
          return second$.pipe(secondSubject$ => {
            return concat(
              merge(
                firstSubject$,
                secondSubject$.pipe(
                  takeUntil(concat(firstSubject$.pipe(ignoreElements()), of())),
                  toArray(),
                  mergeAll()
                )
              ),
              secondSubject$
            );
          });
        })
      );
const first$ = of("first1", "first2");
const second$ = of("second1", "second2");
Dorus
@Dorus
@renke You're missing an publish to create secondSubject
Renke Grunwald
@renke
oh...
Dorus
@Dorus
Like this it will subscribe to second$ twice and idk what effect that has.
Renke Grunwald
@renke
mh, I still see the values from second$ first. Is it a problem that I use of as to create my observables here?
Dorus
@Dorus

@renke https://rxviz.com/v/moY6P51O

works for me.

@renke Oops indeed, looks like that when source2 completes, it instantly emit.
@renke https://rxviz.com/v/38MaX4Y8
source1.pipe(publish(src1 => source2.pipe(publish(src2 =>
  concat(
    merge(
      src1,
      merge(NEVER, src2).pipe(
        takeUntil(concat(src1.pipe(ignoreElements()), of(1))),
        toArray(),
        mergeAll()
    )), src2)
))))
I wonder if i missed a way to simplify this...
Renke Grunwald
@renke
yes, that makes sense, I guess, that would prevent it from completing before src1 completes.
Dorus
@Dorus
yup
toArray react to completion and you dont want src2 completing to trigger that before src1 does.
Renke Grunwald
@renke
I still don't understand why delayWhen is not the right choice here:
      const foo = first$.pipe(
        publish(firstSubject$ => {
          return merge(
            firstSubject$,
            second$.pipe(
              delayWhen(() =>
                concat(firstSubject$.pipe(ignoreElements()), of())
              )
            )
          );
        })
      );
I would imagine that when firstSubject$ completes there is no leakage from delayWhen whatsoever
Dorus
@Dorus
You should test it. But i dont think this will allow second$ to emit once first is done, not after the initial burst.
Idk, does firstSubject$ remember it completed?
Renke Grunwald
@renke
oh, i see the factory is called on each emit of second$?
Dorus
@Dorus
@renke Quick test does show it works. I said nothing :D https://rxviz.com/v/B8ZABXaJ
Actually, thinking back, i think the subject stays in completion status and will emit complete() right away once you subscribe again on new commits from second$
So that's a very neat solution
Renke Grunwald
@renke
it feels a bit more natural so to say
that aside, thanks for your help, I think I learned a lot here, especially about publish
Dorus
@Dorus
Glad to help, i was half asleep yesterday so it's a miracle i gave at least somewhat working code xD
Renke Grunwald
@renke
it certainly pushed me into the right direction, although your shareReplay snippet confused me a bit :-D
Dorus
@Dorus
it's like publish but with a replaySubject backing the inner stream.
Just a ranom brainwave of mine i guess :P
I do like this new found way to using delayWhen. gotta memorize it.
Renke Grunwald
@renke
I am still puzzled why there is no publishReplay that takes a selector function though. Does that not make sense or why does only publish support that.
Dorus
@Dorus
https://rxjs.dev/api/operators/publishReplay does show selectorOrScheduler
@renke
Renke Grunwald
@renke
Oh, I see, maybe was looking at shareReplay which seem to lack it indeed
Dorus
@Dorus
@renke Oops, my mistake. I named shareReplay and i also forgot to set the first 2 params. Idk i always confuse share and publish, even thou i know very well what they do.
Will Mruzek
@mruzekw

Hi there, say I have a high-order observable. It basically contains a set of set of numbers.

I'd like the first inner observable to be listened to until the next inner observable is available. Then the next one should be listened to. I know there's switchMap, but I can't seem to get it to work.

const setOfSetOfNums$ = merge(
  of([4,5,6,7]).pipe(delay(50)),
  of([0,1,2,3]),
).pipe(
  distinctUntilChanged(),
  switchMap(context => of(...context)),
)

zip(interval(1000), setOfSetOfNums$).pipe(
  map(([_, hand]) => hand),
)

I would expect this to output something like:

---0---1---4---5---6---7--->

But it spits out:

---0---1---2---3---4---5---6---7--->

Derek
@derekkite
@mruzekw not quite clear what you need. 0-1-? or 0 - 4 - 5 - 6 - 7 - 1 then what? maybe describe what you are trying to accomplish
Will Mruzek
@mruzekw
I would like the delayed observable to interrupt the non-delayed one
Thus the desired output of ---0---1---4---5---6---7--->
In actuality, it's a user event that generates a new set of nums to listen to, but this should replicate the idea...I think?
If there's a new observable in setOfSetOfNums$, we should immediately switch to that
Dorus
@Dorus
@mruzekw the problem is you zip after switchMap
thus you have them first emit all events at the same time, and then queue up at zip after the switchMap
Observables have no so called backpressure
Derek
@derekkite
of(4,5,6,7).pipe(
    delay(50), 
    switchMap((of(1,2,3,4))
)
Dorus
@Dorus
That's not even valid code
Will Mruzek
@mruzekw
@Dorus There's no way to add any backpressure?
Would it be any different if a click was the trigger to switch observables?
Derek
@derekkite
@mruzekw there are examples of a search bar where the event triggers an http call that is interrupted via switchmap if the user types something more.
Will Mruzek
@mruzekw
To make this even simpler, is there a way to receive a stream of numbers one at a time? Say when I click a button?
Karsten Pruehss
@kpruehss
@mruzekw if you want a stream of individual numbers rather then all the numbers at once, you should use from() instead of of() i think