Skip to content
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

Fix instructions in README.markdown regarding Rails 3.x reloading endpoint per request #324

Merged
merged 2 commits into from
Jan 25, 2013

Conversation

jyn
Copy link
Contributor

@jyn jyn commented Jan 25, 2013

The original instructions didn't work for me on Rails 3.2.11. I used the instructions on the wiki and it works fine (https://github.com/intridea/grape/wiki/Reload-Grape-API-on-every-request-in-Rails).

Edited the README.markdown file to correct this since these instructions caused me to waste time trying to figure out how to get reloading working.

jyn added 2 commits January 25, 2013 13:27
Original instructions didn't seem to work on Rails 3.2.x. Followed instructions
on wiki
(https://github.com/intridea/grape/wiki/Reload-Grape-API-on-every-request-in-Rails)
and it works without issue. In the original instructions, I could only get grape
to reload my endpoint once.

Using this submitted approach looks also looks like a standard way to hook
reloading into any inbound Rails request.
@dblock
Copy link
Member

dblock commented Jan 25, 2013

I'll look into this and test the changes on another app that uses the old code - seems like there're some small variations that make a big difference and depend on the app you have - we have to provide something generic.

@dblock dblock merged commit 3494a60 into ruby-grape:master Jan 25, 2013
@dblock
Copy link
Member

dblock commented Jan 25, 2013

I made some small adjustments around variable naming. Please check it. Thanks for updating, this works as well and is much shorter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants