Autoloading dependencies with Grape as a stand-alone API?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 10k
- Forks
- 1.2k
- Avg merge
- 14h 38m
- Merged PRs (30d)
- 92
Description
All my search efforts and reading of the documentation for Grape seems to indicate that autoloading is a feature provided when Grape is used in combination with another framework, such as Sinatra or Rails. I'm using Grape API as a stand alone application, and with many modules and classes I'm finding I have to explicitly define require_relatives throughout my app.
My question is, does Grape provide an autoloader similar to this out of the box?
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 Grape's standalone usage and dependency-loading documentation, then review the reported use of require_relatives. Done would require a clear decision and documented answer about whether Grape supports autoloading out of the box; no source file, test, or implementation scope is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100