Miller Medeiros

## drop strict/legacy slash behavior the default behavior nowadays is `loose` which I think will be better for most users since it avoids dumb mistakes, haven't seen any case where...

## route groups and filters I'm using Laravel 4 on my current project and [route groups](http://laravel.com/docs/routing#route-groups) + [filters](http://laravel.com/docs/routing#route-filters) are very useful for handling any kind of logic that should happen...

## only normalize fragments as object + pass route/router as argument on handler It was a bad design decision to allow multiple arguments on the route handler, it makes things...

@killmenot I never got the time to work on this, I started working inside bigger projects and mostly maintaining legacy apps.. the last time I used crossroads on any project...

when I need to forward to the default route I use the [`bypassed` signal](http://millermedeiros.github.io/crossroads.js/#crossroads-bypassed) also important to remind that signals are dispatched **synchronously** so you could implement your own method...

at the time bower was still in flux and I didn't want to maintain multiple `*.json` files.. (harder to update/release new versions..) specially since this file was linked to a...

we did some changes to the way query strings are handled, maybe it solved your problem. will release v0.12.2 soon

the main issue here is that I'm using RegExp to generate the routes while I should really be using something smarter to do that.. should not be that hard to...

I made the wrong assumption that `:` was always the end of an optional argument and always going to need `/` in between 2 arguments.

see: https://github.com/millermedeiros/crossroads.js/blob/9e6e24c7c42b85c5e7143c8c881464fa8d1d64d1/dev/src/pattern_lexer.js#L28-L34