You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a blank state rails app created by rails new, API changes in grape seems to be picked up by rails without any modification in application.rb or creating initializer files to listen on callbacks.
I've put the files in correct directory, as per usual in rails, but nothing more.
Adding new apis and modifying existing apis is hot-reloaded without restarting the app.
Is there anything else I need to check to confirm this?
If these instructions are indeed no longer required, I'll create a PR to modify the grape README file.
The text was updated successfully, but these errors were encountered:
FWIW, the only configuration I found to be necessary in Rails 5.1.2 is to mount in config/routes.rb. The autoloader-related change to application.rb was not required.
FWIW I still experience: ArgumentError (A copy of API::V1::Defaults has been removed from the module tree but is still active!)
when I make changes to a definition file without restarting the dev server.
Rails 5.1.7
grape 1.0.3
I mount in config/routes.rb like so mount API::Base, at: '/'
Gem versions
Rails:
5.2.0
Grape:
1.0.3
In a blank state rails app created by
rails new
, API changes in grape seems to be picked up by rails without any modification inapplication.rb
or creating initializer files to listen on callbacks.I've put the files in correct directory, as per usual in rails, but nothing more.
Adding new apis and modifying existing apis is hot-reloaded without restarting the app.
Is there anything else I need to check to confirm this?
If these instructions are indeed no longer required, I'll create a PR to modify the grape README file.
The text was updated successfully, but these errors were encountered: