Rxjs: Error in Operator Decision Tree for switchMap

[Trildar]

Documentation Related To Component:

Operator Decision Tree

Please check those that apply

• [ ] typo
• [ ] documentation doesn't exist
• [ ] documentation needs clarification
• [x] error(s) in example
• [ ] needs example

Description Of The Issue

The Operator Decision Tree relating to switchMap appears to have some issue. It recommends exhaustMap before actually hitting a leaf node and is missing the option for "where the nested Observable is the same for every value". The below screenshot should clarify what I mean.

[dzhavat]

Just tried to recreate this. I started the docs locally and this is what I get when I navigate to the same step:

Can it be that the issue has already been fixed but it's still not deployed yet?

[Fallenstedt]

@jsonberry I think you worked on this right?

[jsonberry]

Yes

I was able to replicate on current deployment, not sure of the version

It’s possible that the only thing required is a fresh generation and
deployment of the JSON that runs the ODT, and not a version bump on the
docs app itself

Haven’t looked into actual debugging yet, will attempt to do that soon
unless someone else with deployment powers can take a look at it

On Fri, Dec 6, 2019 at 9:16 AM Alexander Fallenstedt <
[email protected]> wrote:

@jsonberry https://github.com/jsonberry I think you worked on this
right?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ReactiveX/rxjs/issues/5154?email_source=notifications&email_token=AAXQSKFEDMINAT4REQ7WD5TQXKCGNA5CNFSM4JPP3GF2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGEYHEA#issuecomment-562660240,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXQSKAC7J5W2DSYND2TAQLQXKCGNANCNFSM4JPP3GFQ
.

[dzhavat]

@Trildar the docs were updated earlier today. Can you check if you still get that error? :)

[jsonberry]

On version 6.5.5-local+sha.7e4589a1 of the docs released to prod I'm unable to reproduce the bug, poked around a bit on it and haven't seen any issues.

[dzhavat]

If that's the case, can the issue be closed?

[Trildar]

Hi, sorry, forgot to check on this. Seems fine checking on my phone, albeit that's not what I used when I noticed the issue. Will try to check on that if I remember.

[Trildar]

Checked on the platform where I first encountered the issue. Seems to be fixed. Though I did have to reload the page once, likely due to cache.

[dzhavat]

In that case the issue can be closed :)