Iron-router becoming incompatible. Switch to flow-router or wait for MDG router?

Yeah you are right, but you should add them because it is possible that the user changes the routes and goes back. In that case the data stays and there should be no flickering.

Do you use a loading icon while you are waiting for your subscription?

I’m new to meteor and am using flow router. I’ve found it dead simple if you understand routing In general.

I like flow-router too. It’s well done, so MDG might not need to make their own(or at least flow-router makes it less priority for MDG).

1 Like

I’ve only so far used the recommended solution where you remove the current content with a loading icon and then replace that with new content when the subscription is ready using a template helper.

I’ve not found a nice solution similar to youtube.com where on page load you would wait for some subscriptions like the main content and have a loading bar at the top and let other subscriptions load async like comments and related videos.

FlowRouter claims to provide a better solution on routing and subscriptions but I’m finding atm it just gives you less options. :confused:

1 Like

This has been said many times before about many different routers. It’s the reason there’s a pantheon of packages that depend on routers X, Y, and Z. It’s the reason why it’s so frustrating to see a cool package that does whatever, only to find it uses a different router than yours.

MDG not providing a routing solution has proven to be a bad idea.

Flow router is currently the official Meteor router.

8 Likes

This is a wise decision although I need to migrate my Iron Router to Flow Router.

@arunoda can you recommend any tutorials a la ‘Getting Started With Meteor’ that use flow router, opposed to IR?

The meteor guide uses FlowRouter ( http://guide.meteor.com/routing.html ), as does its companion example app: https://github.com/meteor/todos.

Mantra’s example app does too: https://github.com/mantrajs/mantra-sample-blog-app

1 Like