broken?: Match a route with `:param` parameters base inside nested configurations

[wmaurer]

I'm struggling with a variation of one of examples from the README:

const { path, value } = switchPath('/1736/home', {
    '/bar': 123,
    '/:id': {
        '/': id => `id is ${id}`,
        '/home': 789
    }
});
console.log({ path, value });

I was expecting to get:

{ path: '/1736/home', value: 789 }

But I'm getting

{ path: '/1736', value: 'id is 1736' }

Using an older version of switch-path (1.1.0), I'm getting:

{ path: '/1736/home', value: 'id is 1736' }

... also not what I expect.

[wmaurer]

I might be able to find some time to try to rectify this and make a PR, but I'd first like to know if my understanding is correct. Is the behaviour of the current version of switch-path correct as designed, or should it work according to my expectation as above?

[TylorS]

Yea, you should be getting what you expect

[wmaurer]

Ok, so I started looking into this and I wasn't able to find a easy solution to this problem. I have a feeling the problem is caused by the requirement to satisfy the unit test 'should match a path on an incomplete pattern'. I don't believe there is an easy fix to the bug reported above.

The thing is, my routing requirements are (at the moment) satisfied by another very small and simple library ruta3. The problem with ruta3 is its API, which is far from compatible with cyclic-router.

So I embarked on a small project which wraps provides the ruta3 routing functionality in switch-path's API: switch-path-ruta3.

There are some switch-path unit tests which fail with switch-path-ruta3, but there are also a couple extra which would fail with switch-path (see here - the failing tests are skipped, and there are a couple extra).

I am considering publishing switch-path-ruta3 on npm as an alternative to switch-path, but I thought I'd post here first to gauge the reaction, specifically from @staltz and @TylorS. My intention is not to cause any annoyance by publishing an alternative, simply to allow others to use a solution that works for me.

Your feedback is welcome.

[wmaurer]

So it seems that the priority of this repo is rather low at the moment ... no problem ;-)

As I've mentioned, I'd be willing to work on a fix, but I don't believe I can satisfy my requirement without breaking the API of this library. I'd rather wait until there is buy-in from the project owners.

In the meantime, I've published my first ever npm package: switch-path-ruta3 in case anybody has the same requirement as I do.