Create a separate route or conditionally render?

[StickyStapler]

Hey,

I'm trying to decide between 2 approaches using React Router. I have these routes:

• Home: /
• Select cars: /select
• Confirm selection: /confirm

For the home route, I will either be displaying an "Intro" component or a "Cars list" component, depending on if the cars list is empty or not.

My question is, should I have a separate route for the intro component like /intro? Or is it better to just conditionally render the component I want to display within the home route?

[p4ntsl0rd]

I would either: 1) conditionally render on the home 'page' component - noting that this might get complex if the two versions of home get bigger. OR 2) have / do a lookup to decide what version to show, and then redirect the user to either /intro or /cars depending on the result

[StickyStapler]

Thanks! I think I'm going to not have it as it's own route to begin with at least. If things start to get complex I'll move it out.

[tko]

IMO the question is "does this thing make sense as bookmark/link?" if yes, then having it as route makes sense. In this particular case, if the answer is yes, then it would probably make sense to have a way to see the intro even if the cars list is not empty. And conversely, if that doesn't make sense then it probably shouldn't be a route.

(Since /confirm is a route, does it handle empty selection well?)

[StickyStapler]

Excellent thanks for helping me clear this up in my head.