jamesplease / jamesplease/gistbook
Log stack trace in route error callback
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 88
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
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 by locating the route error callback in the JavaScript application and inspect how route errors are currently handled. Add stack-trace logging there, then verify that an error produces the expected trace in the application's logging output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100