Rails reloading instructions no longer required?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 10k
- Forks
- 1.2k
- Avg merge
- 14h 38m
- Merged PRs (30d)
- 92
Description
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 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Rails reloading instructions in the README and reproduce the report in a blank app created by rails new using the stated Rails 5.2.0 and Grape 1.0.3 versions. Check whether API additions and changes are picked up without application.rb changes or initializer callbacks; done means confirming whether the instructions are still required and identifying the README text that should change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100