SLF4J Logging Warnings
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 101
- Forks
- 9
- Avg merge
- 13m
- Merged PRs (30d)
- 1
Description
When I trying running a simple http4s client app with Typelevel Toolkit, I get warnings about SL4FJ at startup:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
I can get rid of them with //> using dep ch.qos.logback:logback-classic:1.5.3
Maybe the toolkit should include a default logging implementation out of the box? I have no interest in remembering to configure logging when I'm trying to do a quick script.
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 by reproducing the startup warnings in a simple http4s client app using the Typelevel Toolkit. Compare the current toolkit setup with the suggested //> using dep ch.qos.logback:logback-classic:1.5.3; done should mean the default setup no longer emits the SLF4J warnings without requiring users to configure logging themselves.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100