-
Notifications
You must be signed in to change notification settings - Fork 19
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
[feature] Grape routes #24
Comments
Hi. |
This works but it can't seem to parse the path/action correctly. I think it's because they are different formats. The verb is being detected perfectly fine though. |
This is what the output looks like on each line, method, endpoint path, api version, description Majority of endpoints use the api version at the beginning and all use (.:format) at the end.
|
Hmmm... I see. Thank you for the information. While it's not hard to parse string of this format, but I need to find all possible formats of route output to parse well, otherwise output may be messy. Could you please provide more samples? |
This is the only other thing i can think of, it's a base route so it doesn't have a api version. the url variables (:variable) can be anywhere in the route with as many of them in it.
|
There is a gem called "grape_on_rails_routes". It would be nice if this gem is installed (or a setting to change) to use "rake grape:routes" so this plugin will pick up routes from grape instead.
The text was updated successfully, but these errors were encountered: