ruby-grape / ruby-grape/grape-swagger
Cache response
Open
Nobody has claimed this yet.
new feature
swagger-1.2
- Dominant language
- Ruby
- Stars
- 1.1k
- Forks
- 479
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 6
Description
Even with #161 fix, rendering can take a few seconds. Feature request: cache the response in memory as it doesn't change until server restarts anyway.
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 by reading issue #161 and tracing the response-rendering entry point in the repository; the issue names no files or tests. Done means the response is cached in memory, remains unchanged until server restart, and avoids repeated rendering work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100