@jasonLaster Personally (and I may be wrong), if I was depending on `appRoutes` for logic I would expect it to contain anything from `processAppRoutes`. So I'd say it would be breaking for people depending on it to have an unusual behavior, but I digress.

If `appRoutes` is not the place for it, or project maintainers don't want to change it's meaning/behavior, I'd suggest adding appRoute properties onto `Backbone.history.handlers`.

Everything is already being added there by `Backbone.history.route` [here](https://github.com/jmeas/backbone.marionette/blob/add-onRoute/src/marionette.approuter.js#L75), and extending it with new properties would avoid breaking code while creating a collection of all routing information.

Or you can add a new private property somewhere, that's always an option.

This discussion could probably be taken into another issue. I don't think theres anything wrong with this PR (except for the failing build).