-
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
Can't get started #51
Comments
I have the same issue. |
Same issue. I've copied the entire blocks of missing definitions and am not seeing any of them as actual API routes. Rails 4.01 |
Hmm, I'm not using it in our rails 4 app so I can't be sure what's going on. Anybody wanna take a look and see if it's easily fixable? :) |
It looks like @jtomaszewski is able to get it working on his Rails app. #49 Might be good to see if there is anything that needed to be added in an initializer or in Rails routes/config. |
@fredwu, what starting point can I look at in the lib/engine to see why it is not picking up our Rails 4 routes which are defined exactly per README? |
So what worked for me was to set the following value in an initializer ApiTaster.route_path = Rails.root.to_s + "/config/api_doc" then in that directory I created a routes.rb file with the API definition files per the instructions. I suspect a "routes" method was added in rails4 that is causing the issue. I'll dig into it when I get some free time and submit a pull request with a fix. |
Same issue for my rails 3.2.16 app using api_taster (0.7.0) |
Looks like it works fine with api_taster (0.6.0) |
I have the same issue on Rails 3.2 |
It worked for me on Rails 3.2 with the following ref: gem 'api_taster', '0.6.0', git: 'https://github.com/fredwu/api_taster.git', ref: '31c6f51' |
Connected to #45? |
Yes is related to #45, code was already merged and new gem will be pushed to ruby gems soon. |
I'm having this same issue with a new Rails 4.1 app, even with my Gemfile pointed to the master branch. |
@andyw8 try to use latest api_taster gem version - that is what I'm using in my projects - also please review latest changes on README. In your routes.rb file you should only mount api_taster engine:
Then create a file app/api_tasters/routes.rb this is the place where you should define your API routes for api_taster. Finally add an initializer like this:
|
Thanks for your help. I'm using 0.8.2, the latest release. I have the api taster routes file in the default location so there so should be no need for an initializer (I tried just in case but it made no difference). You say in my routes file I should mount only ApiTaster::Engine but I don't see any mention of this in the README. Where are my other routes supposed to go? |
I can't get api_taster to run. I can only see
Warning Missing Definitions Detected
I didn't define any routes at first, and only added
then I defined routes
Still both cases it doesn't work, so i tried outside
routes.rb
Is there anything i'm missing? I'm using rails 4 btw. Also i'm using api-versions
The text was updated successfully, but these errors were encountered: