MichalLytek / MichalLytek/type-graphql
Debug logs
- Dominant language
- TypeScript
- Stars
- 8.1k
- Forks
- 672
- PR merge metrics
- No merged PRs in 30d
Description
**Is your feature request related to a problem? Please describe.**
This is related to #12. Because the error messages at times are cryptic as things get fixed related to that issue; it might also be good to have debug logs available when needed so one can trace through the problem.
**Describe the solution you'd like**
I see loggers in the examples, something similar with different log levels using `winston` or something else.
**Describe alternatives you've considered**
Currently I am looking at the source code to trace through the issues.
Contributor guide
Research direction
Start by reading the related issue #12 and the existing logger usage in the examples, then trace the relevant source code paths. Define the logging entry points, levels, and expected output before implementing anything; done means users can enable debug logs to trace the errors described by this issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- backend-api-design, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100