Kevin Ross

It looks like this is confirmed to be unrelated to state_machines. Even though state_machines will be somewhere in the call stack, it seems to be other gems or an AR...

Along these lines, I'm trying to `enzyme` `mount` and need the router. Since I'm using a link, it fails with the simple spy-based router. So +1 for exposing a test...

The result of `makeRouteConfig`: ```tsx [ { children: [ { path: '/:tenantName', children: [ { children: [ { path: '/:tenantName/' } ] } ] } ] }, ] ``` Yet...

So this works, verifying that `path` is additive: ``` import('./DashboardPage'))} /> ``` https://acme.com/mytenant/dash It seems like the router is bailing out before traversing to my `/` route - like it...

Thanks @taion - I verified they are additive, but my nested `/` path is not accessible. I plan to nest a bunch of routes under `` but certainly the tenant...

That does work - thanks! Seems a bit strange at first glance but perhaps understandable since it is the exact same as the parent.

Trailing slash didn't work. I tried that above. If nested `path='/'` it never renders regardless of url e.g. - https://acme.com/mytenant - https://acme.com/mytenant/ I can work with the omitted `path`.

NP, we can reopen if you like, I just want to help avoid clutter.

I just simplified the case, still same problem as soon as files are split. I cannot spot the problem.

Even stranger, I used/exported the `Test1` from `allInOne.js`, just to see if it would work in `index.js`, and it does. ```js import ClassTest from './ClassTest' import Test1FromAllInOne from './allInOne' const...