-
Notifications
You must be signed in to change notification settings - Fork 13
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
Generate grape doc for non-rails project #1
Comments
Thank you for feedback. P.S. there is a lot of features, that I want to implement, but so little time. |
I've publish version with hotfix right now, source code stores at Will you open Pull Request? If not, then I merge |
Thank you so much for fast turnaround, please go ahead and merge. |
actually i just created a pull request. so the merge can be done easier. |
I'd never worked with Sinatra or other non-rails rack app, so, please, tell me about any problems, if they presents. |
yup, i will do some testing and see how it works maybe come up with a wiki page. |
Great, thanks. |
it works for me, donno if it worth a wiki, my projects follows the standard gem structure, I specified the --path to the file under my lib/mai.rb file. it loaded the classes and generated the doc for me. Thanks for your help |
That's great, I'm glad that you found it useful. |
I have a Grape/Sinatra app using rack following standard gem directory structure.
currently grape_doc is looking for config/environment which is missing for a non-rails project.
It will be nice if grape_doc can support generic grape project or using a command-line flag to specify the type of the project.
Thanks
The text was updated successfully, but these errors were encountered: