We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello!
The example below shows that a trace log is evaluated even if the level (debug) should not allow that.
sbt: 1.10.3 scala: 3.5.2 scribe: 3.15.1
import org.scalatest.freespec.AsyncFreeSpec import cats.effect.testing.scalatest.AsyncIOSpec import org.scalatest.matchers.should.Matchers import scribe.* class ScribeTest extends AsyncFreeSpec with AsyncIOSpec with Matchers: Logger.root.withMinimumLevel(Level.Debug).replace() "scribe" in: trace { println("no good") "trace log" } "a" should be("a")
output:
testOnly *Scribe* no good [info] ScribeTest: [info] - scribe
The text was updated successfully, but these errors were encountered:
If you do:
scribe.info(LogFeature.logOutput2LoggableMessage { throw new RuntimeException("Should not evaluate!") "testing" })
It works as it should. There's a problem with a change I made for varargs on LogFeatures apparently.
Sorry, something went wrong.
6cd1a2a
See release 3.15.2
great! Thank you!
darkfrog26
No branches or pull requests
Hello!
The example below shows that a trace log is evaluated even if the level (debug) should not allow that.
sbt: 1.10.3
scala: 3.5.2
scribe: 3.15.1
output:
The text was updated successfully, but these errors were encountered: