Multiple routers with backbone.js

backbone.js router
Industrial picture Industrial · Jan 22, 2012 · Viewed 7.9k times · Source

Can I use multiple routers in backbone.js, that don't interfere with each other route-wise, without any issues? Or is there something that I should be concerned about?

Code sample:

myapp.routers.main = Backbone.Router.extend({
    routes : { "": "index" },
    index : function() { console.log("routed by main router");}    
});

myapp.routers.another = Backbone.Router.extend({
    routes : { "notmain": "index" },
    index : function() { console.log("routed by another router");}    
});

mainrouter = new vaikava.routers.main;
notmainrouter = new vaikava.routers.another;
Backbone.history.start();

Answer

taxilian picture taxilian · Jan 22, 2012

Yes, it works just fine; the only time you'd have a problem is if they have conflicting routes. There is a workaround that makes it work that way as well, but it's a bit of a hack.

As long as you avoid having multiple routers trying to handle the same route you should be fine.

Related questions

Is there a way to catch all non-matched routes with Backbone?

I want to have a 'catch all' route which runs when none of the other defined routes are matched. A type of 404 NotFound error handler. I've tried adding this, which works but prevents other routes from matching: this.route(/(.*)/, 'notFound', …

Read More
Multiple routers vs single router in BackboneJs

All examples on Backbone I've seen use one router for the whole application, but wouldn't it make sense to have a router for each single part of your app (header, footer, stage, sidebar)? Has anyone built apps with more than …

Read More
Backbone router with multiple parameters

I need to get this to work: routes: { ':product' : 'showProduct', ':product/:detail': 'showProductDetail' showProductDetail never gets called while the ':product' route is set even if it is set afterwards. I tried the following routes: { ':product(/:detail)…

Read More