Add triggers support for notFound routes

When I add a notFound handler I would expect it to also support triggers because it mimics the interface of the normal routes. But if I go to a unknown route with following notFound handler:

function trigger () {
    debugger;
}

FlowRouter.notFound = {
    triggersEnter: [trigger],
    action: function() {
        debugger;
    }
};

The triggersEnter doesn’t get executed at all.

This is clearly a problem for me as I want to do a hard browser load on the requested not found url. But the action handler doesn’t have the context of the original request just the ‘*’ route.

[Lepozepo]

You can do it via the Meta package and use it through the action function. There you can set the status code to 404. Here’s my snippet

FlowRouter.notFound =
    action: ->
        if Meteor.isClient
            Meta.set [
                {
                    name:"name"
                    property:"prerender-status-code"
                    content:"404"
                }
                {
                    name:"name"
                    property:"robots"
                    content:"noindex, nofollow"
                }
            ]

        BlazeLayout.render "layout",
            content:"not_found"

[Lepozepo]

I’ve learned a lot from you, I’m glad to help out when I can ^_^