ParseableRoute - abstraction for routes and support for Rails 3.1 #38
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I experienced the same problem as in Issue 26, where normalise_routes! was throwing an exception parsing my routes - "undefined method `source' for "GET":String".
My app is running Rails 3.1.10, and I found that the issue stemmed from the difference between the ActionDispatch::Routing::Route objects in Rails 3.1 and the newer Journey::Route objects in Rails 3.2.
Rather than add a bunch of conditional logic inside Route.normalise_routes! and Route.normalise_route, I wrapped the Rails routes in an abstraction which handles the differences in the interfaces between an ActionDispatch::Routing::Route and a Journey::Route, such as #verb being a String in the former and a Regexp in the latter. For me, this resolved the error from Issue 26 and got my routes all parsed correctly.