Refactor Rack dependency
Open
Nobody has claimed this yet.
discuss!
- Dominant language
- Ruby
- Stars
- 10k
- Forks
- 1.2k
- Avg merge
- 14h 38m
- Merged PRs (30d)
- 92
Description
Grape is in many parts depentend from Rack. Like this post show's Racks future is uncertain. In my point of view grape should plan ahead and decouple from Rack as much as possible.
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
The issue names no files or tests; start by mapping where Grape depends on Rack across the repository and read the linked Rack discussion for context. Done would require a clearly scoped, agreed plan to decouple Grape from Rack as much as possible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100