Multiple routes trigger first one to fire multiple times

[rvision]

I have a following code:

routie('search/:text', function(text) { ... });
routie('view-group/:id', function(id) { ... });
routie('view-test1/:id', function(id) { ... });
routie('view-test2/:id', function(id) { ... });

When reloading a page, first handler ('search/:text') when route is matched is fired 4 times, for each route declared. If I remove view-test1 and view-test2, it is fired 2 times.

Is this a serious bug?

[rvision]

It seems that this happens in

-latest Firefox (v31.0)
-IE 11

works fine in Opera

[ollyoechsle]

By coincidence I also noticed this today. Looking at the source the way to do it is to call routie once, passing in an object if there are multiple routes.

routie({
'search/:text': function(text) { ... },
,'view-group/:id', function(id) { ... },
,'view-test1/:id', function(id) { ... },
,'view-test2/:id', function(id) { ... }
});

Would it be possible to make this clearer in the docs? Perhaps Routie could also print a console warning stating that init should only be called once?

Otherwise it is a great product, and I use it often. Thank you for developing it.

[rvision]

Doesn't work for me, I need routing in multiple modules...

[carsonwright]

I'm having this problem too, I'm on chrome, and the first time it loads it tries to execute 3 times.

[rubenspgcavalcante]

I need to declare each one in the index of each module.
Each time I declare a route, the other ones already declared is fired by the number of declared routes.
Ubuntu Firefox v32.0

update:
I've made a pull request. After all routie declarations, with last param (forceCheck) as false, explicitly call the reload using apply. e.g.:
routie('search/:text', function(text) { ... }, false);
routie('view-group/:id', function(id) { ... }, false);
routie('view-test1/:id', function(id) { ... }, false);
routie('view-test2/:id', function(id) { ... }, false);
routie.apply();

[NicholasEymann]

I have opened a pull request that fixes this issue. #47

[CtrlC-Root]

@NicholasEymann Thanks! I'll take a look at it soon and get back to you in the actual pull request.