Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ParseableRoute - abstraction for routes and support for Rails 3.1 #38

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

robbjl
Copy link

@robbjl robbjl commented Feb 9, 2013

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.

… classes

This class will be used to create a consistent API for api_taster/route to use when parsing routes, in order to better support different versions of Rails (notably 3.1 which uses ActionDispatch::Routing::Route instead of Journey::Route)
@fredwu
Copy link
Owner

fredwu commented Feb 11, 2013

Nice! Could you please update the code to use hash rockets so that it passes Travis's ruby 1.8.7 build? Thanks! :)

@robbjl
Copy link
Author

robbjl commented Feb 11, 2013

Sure, sorry about that. Been using 1.9.3 exclusively for so long I forgot about them!

@fredwu
Copy link
Owner

fredwu commented Jul 19, 2013

Hi @robbjl thank you so much for the PR! Sorry I haven't had a chance to review this for such a long time. Is your app still on rails 3.1? I am undecided on this PR as rails 4.0 is now released, and I personally don't have any rails 3.1 apps around. Hence I'm probably in favour of dropping support for 3.1.

Having said that, if you could rebase this PR I will merge it in! :)

@mariochavez
Copy link
Collaborator

Hi @robbjl is this patch still need it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants