Simplify even more? about flow-router HOT 7 CLOSED

You should not use this.register inside the action. I you can that's a bug in Flow Router.

There is a reason for that we've a subscriptions in the router.

• We believe subscriptions are aligned to a route most of the time.
• For fast-render we need to run subscriptions on the server

That's why we have something like this.
But, we don't need to wait for subscriptions. That's why we only register it. Later you can check for the status.

And we've .ready()API which can check for the readyness for multiple subscriptions at once. It's simple useful helper function.

from flow-router.

Thanks @arunoda, understood.

My feeling is that maybe there is a simpler way to use your package that what is explained in the doc (for those who don't use fast-render and don't attach subscriptions to routes). I'll try to write an alternate manual if I have time.

Regarding the ready API, since I never attach subscriptions to a route, I use Template.subscriptionsReady instead.

from flow-router.

You need to have action method for the route. Otherwise you need to do some logic to pick the route and do the rendering.

from flow-router.

Yes. You can leave it alone. Both subscription and action are optional. May
be I can add it to docs.
On 2015 මාර්තු 12, බ්‍රහස් at ප.ව. 7.25 steph643 [email protected]
wrote:

Thanks @arunoda https://github.com/arunoda, understood.

My feeling is that maybe there is a simpler way to use your package that
what is explained in the doc (for those who don't use fast-render and don't
attach subscriptions to routes). I'll try to write an alternate manual if I
have time.

Regarding the ready API, since I never attach subscriptions to a route, I
use Template.subscriptionsReady
https://github.com/meteor/meteor/blob/devel/History.md#blaze instead.

—
Reply to this email directly or view it on GitHub
#34 (comment)
.

from flow-router.

Yeah. I am quite happy to add a link to that manual on the read me.
On 2015 මාර්තු 12, බ්‍රහස් at ප.ව. 7.30 Arunoda Susiripala <
[email protected]> wrote:

Yes. You can leave it alone. Both subscription and action are optional.
May be I can add it to docs.
On 2015 මාර්තු 12, බ්‍රහස් at ප.ව. 7.25 steph643 [email protected]
wrote:

Thanks @arunoda https://github.com/arunoda, understood.

My feeling is that maybe there is a simpler way to use your package that
what is explained in the doc (for those who don't use fast-render and don't
attach subscriptions to routes). I'll try to write an alternate manual if I
have time.

Regarding the ready API, since I never attach subscriptions to a route,
I use Template.subscriptionsReady
https://github.com/meteor/meteor/blob/devel/History.md#blaze instead.

—
Reply to this email directly or view it on GitHub
#34 (comment)
.

from flow-router.

I was going to ask something similar: since you can run any code in subscriptions, you can run rendering as well. Then what is the point of action?

FlowRouter.route('/blog/:postId', {
    subscriptions: function(params, queryParams) {
        this.register('myPost', Meteor.subscribe('blogPost', params.postId));
        FlowLayout.render('componentLayout', {content: ...});
    }
    // no need for `action`
});

I'm new to Flow-Router, so please pardon my ignorance :)

from flow-router.

subscriptions is different. I runs inside a autorun for managing
subscriptions (auto unsub.)
It also runs on the server.

Actions is a simply a function.

On Thu, Jun 4, 2015 at 4:36 PM Dan Dascalescu [email protected]
wrote:

I was going to ask something similar: since you can run any code in
subscriptions, you can run rendering as well. Then what is the point of
action?

FlowRouter.route('/blog/:postId', {
subscriptions: function(params, queryParams) {
this.register('myPost', Meteor.subscribe('blogPost'

, params.postId));
FlowLayout.render('componentLayout', {content: ...});
}
...
});

I'm new to Flow-Router, so please pardon my ignorance :)

—
Reply to this email directly or view it on GitHub
#34 (comment)
.

from flow-router.