ruby-grape / ruby-grape/grape

Autoloading dependencies with Grape as a stand-alone API?

Open
#1,834 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.