Just tested this.

If I add .add('redirect', '/test-route/:queryparams') to routes, links like:

http://localhost/test-route?queryparams=param

work, if I put .add('test-route', '/test-route/:queryparams', 'test-other-route') the link above leads to a 404. Only links like:

http://localhost/test-route/param

Will work. Is this intended behavior?

It might be nice to have build in existence checking for a route

Expected Behavior

Right now I've just added a global mixin

routeExists(name) {
    try {
        route(name)
        return true;
    } catch (Err) {
        return false;
    }
},

On occasion I want to check if a route exists before offering a to the user.Having a convenient way to check it is always a

I'm submitting a ...

• bug report
• feature request
• other (Please do not submit support requests here (below))

The Router Challenge aims to be to Routers what TodoMVC is to MV* frameworks. It offers the same Music Catalog application built in React using different Routers. For it to be succe

What is your feature request
Support Carthage dependency manager
https://github.com/Carthage/Carthage#supporting-carthage-for-your-framework

What problem would it solve
Allow developers who use Carthage dependency manager to take advantage of XRouter

For now a regex is hardcoded it is used to parse nested routes:

  let re = new RegExp(':([^\\/\\?]+)\\??', 'g');

It would be nice to be able to specify it if it should be something else than the default

Description
It's not a bug. I've found a way to use the link function in a simpler way. The createRouteLinks function returns an object with only one function inside and I think this can be changed.

Describe alternatives you've considered
Return a function instead of an object, to simplify the usage. ⚠️ It will break the library API.

Related code:
https://github.com