rubyforgood / rubyforgood/alongwithyou
Move `unmatched_route` out of the abstract base controller
Open
Beginner friendly
Nobody has claimed this yet.
good first issue
severity:minor
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 4
- Avg merge
- 9h 34m
- Merged PRs (30d)
- 16
Description
It's a public method on Api::BaseController, so it's an inherited action on every API controller, confirmed Api::V1::TasksController.action_methods includes it. No route reaches it, but it belongs in a small dedicated errors controller rather than the abstract base.
Contributor guide
No contributing guide indexed for this repository
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 Api::BaseController and inspect Api::V1::TasksController.action_methods to confirm how unmatched_route is inherited. Move the method into a small dedicated errors controller, then verify that API controllers no longer expose it as an action and that no route reaches it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails
- Domain
- api, backend
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100