Store route on trie node

[tornqvist]

This reverts #66 in favor of storing the route on the trie node. Using a proxy callback worked for mitigating the immediate problem with reusing route callbacks but it also makes it difficult to register anything other than functions as route callbacks.

I.e. if I was to register a class as a route callback I'd probably want that class returned from .match and not a wrapper function. This is relevant if you'd want to register top level components as routes in choo.

This does however break the undocumented functionality of accessing the route on this in the callback. I dunno what that means for semver 🤔

[yoshuawuyts]

This does however break the undocumented functionality of accessing the route on this in the callback. I dunno what that means for semver thinking.

Ghmmm, yeah good one. We did make for an explicit patch to add this at some point - but I don't believe I ended up using it anywhere in Choo source.

I'm leaning towards ignoring it, and we'll hear it if it breaks. It's a quite small feature, and like you're saying: undocumented.

[goto-bus-stop]

We can conservatively do a major for this and use it in Choo 7 @tornqvist