-
Notifications
You must be signed in to change notification settings - Fork 85
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
Getting routes within devise_scope #28
Comments
i too am experiencing difficulties w/ devise routes not appearing in api_taster |
as fyi, i've created a forked version of the project to enable devise_scoped routes to appear. essentially commenting the line 38 in lib/api_taster/route.rb regardung ActionDispatch::Routing::Mapper::Constraints does the trick for me. here's the fork: https://github.com/adamlutz/api_taster I'm sure there's a good reason the original developer chose to skip over these types of routes, which I'd be curious to understand why. as fyi, my forked version also simplifies much of the api_taster interface for my purposes of testing a json only API. |
There is an open pull request (#35) for it, but I'm just trying to remember why I did put this line in in the first place. :) |
👍 for this |
Fixed via #35 |
I am using devise to handle authentication.
Routes within devise_scope are not detected by api_taster in my Rails routes file.
any advise on how to make api_taster working with this case ?
I had a brief look at Rails routes,
Rails.application.routes.routes returns the routes with the following constraint:
@constraints=[#<Proc:0x007fa54c0dfd88@ .../gems/devise-2.1.2/lib/devise/rails/routes.rb:338 (lambda)>]
how does api_taster work on parsing the routes.rb file ?
the spec draft should be something like this
The text was updated successfully, but these errors were encountered: