Move `unmatched_route` out of the abstract base controller

Open Beginner friendly
#90 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Quiet
Tech stack
rails
Domain
api, backend

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.

Description

good first issue severity:minor

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.

Dominant language
TypeScript
Stars
9
Forks
4
Avg merge
9h 34m
Merged PRs (30d)
16

Contributor guide

No contributing guide indexed for this repository

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.

More from rubyforgood/alongwithyou

All issues in rubyforgood/alongwithyou

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.