rubyforgood / rubyforgood/alongwithyou
`/api` and `/api/` return HTML 404 instead of JSON
Open
Beginner friendly
Nobody has claimed this yet.
good first issue
severity:significant
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 4
- Avg merge
- 9h 34m
- Merged PRs (30d)
- 16
Description
Verified 404 text/html for both. The catch-all at config/routes.rb:15 is /api/*unmatched, and a wildcard segment needs at least one character, so the namespace root falls through to the HTML 404 page. Add an optional glob or an explicit route.
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
Inspect config/routes.rb:15 and reproduce requests to /api and /api/ to confirm their current HTML 404 responses. Adjust the routing as described in the issue, then verify that both namespace-root paths return JSON 404 responses.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rails, ruby
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100