How to match child route and parent sibling <Fragment>s simultaneously

[granmoe]

<Fragment forRoute="/foo/bar">
  <SomeComponent/>
</Fragment>
<Fragment forRoute="/foo">
  <Fragment forRoute="/foo/bar">
    <SomeOtherComponent />
  </Fragment>
  <Fragment forRoute="/foo/baz">
    <YetAnotherComponent />
  </Fragment>
</Fragment>

There currently is no way to show the first /foo/bar Fragment and the nested /foo/bar Fragment at the same time. We ended up using a hacky solution of looking at the router state in connect in order to determine what page we're on, and then using this to conditionally show the appropriate UI for that route in the equivalent of the first /foo/bar Fragment in our code. It would be nice to have some kind of wildcard match sort of like /foo/:childRoute that would be able to be matched simulataneously with /foo/bar, but I'm not sure if such a thing exists based on the documentation.

[gertsonderby]

Fragments nest their routes, so you'd want a structure more like this:

<Fragment forRoute="/foo/bar">
  <SomeComponent/>
</Fragment>
<Fragment forRoute="/foo">
  <Fragment forRoute="/bar">
    <SomeOtherComponent />
  </Fragment>
  <Fragment forRoute="/baz">
    <YetAnotherComponent />
  </Fragment>
</Fragment>

That should work, I think. All else failing, of course, there's withConditions, which I've used as an escape hatch a couple times for odd routing needs.

[granmoe]

Interested...I was able to get that to work in codesandbox

You may have just solved our problem and eliminated this chunk of tech debt for us :-) Will try this at work soon and close this issue if it works. Thank you!