Route conditions must be static about nancy

[grumpydev]

I'm not sure about them having to be static, but this is definitely "by design". The idea of the route filter is to take a look at the incoming request (or the context in the context branch) and make a decision about whether the route is acceptable or not. The canonical example is being able to have a route for mobile devices, and a route for desktop devices. I'm not sure what the use case is for needing to have the module initialised to make that decision?

The fact that the module isn't initialised when the filter is run is the big advantage of the implementation. As has been discussed on the forum before, we don't want to spin up multiple modules to handle a single request, as that's expensive. It's arguably less expensive with the context additions, but it's still expensive.

Can you give some use cases why this doesn't fit the bill? Perhaps take it onto the forum for discussion - changing this is not something that should be done lightly imo.

[thecodejunkie]

lucisferre - I, like Grumpy, would love to see some real use cases for this. Could you post a couple? Thanks!

[chrisnicola]

It really isn't as big a deal since the addition of the before/after filtering so I'll just close it. There really are no important use cases for this for me anymore.