Do not log 404 requests
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
404's throw via got and are added to the client log when there is no problem and this is expected behavior. Filter out 404 requests from the logs.
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 at src/services/geocode.js around line 174, where 404 responses from got enter the client log. Trace the existing logging path and confirm that expected 404 requests are the only entries to exclude. Done means 404 requests no longer appear in the client log while other relevant errors continue to be logged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 58/100