override createMessage in LoggerPrinter like this:

1:
// return args == null || args.length == 0 ? message : String.format(message, args);
if (args == null || args.length == 0) {
return message;
}
String pattern = "(%\d)?$(a|b|c|d|e|f|g|h|n|s|tx)";
Pattern p = Pattern.compile(pattern);
Matcher m = p.matcher(message);
if (m.find()) {
return String.format(message, args);
} else {
t(me

Please visit the contributing guidelines to learn more on how to translate Signale's documentation into more languages.

Tons of thank you to everyone for your help and support! ❤️

I like the language about legacy versions and how they are are supported in https://github.com/googleapis/google-cloud-node#supported-nodejs-versions . I think we could adopt some form of it.

Set a reasonable default and then grow accordingly, instead of defaulting to a pretty large offset which looks kind of silly in simpler cases.

Hello,
Do you know about Conan?
Conan is modern dependency manager for C++. And will be great if your library will be available via package manager for other developers.

Here you can find example, how you can create package for the library.

If you have any questions, j

The documentation generator at ./docs/generator/ could support the config struct tags introduced in trivago/gollum#143 to:

• Detect undocumented configuration parameters and include them in the documentation
• Detetect and warn about inexistent / mistyped configuration parameters found in the doc comments

Not a very urgent need, but perhaps useful when revising do

I have used this library and its not capturing Swift run time exception or traces. This is only handling Objective C exception. If you could help me out for showing Swift run time exception with stack trace.

Detailed Description

The docs should correctly state that Micronaut supports the use of Logbook's Netty module.

Context

Currently Surface.of[X] automatically consume ClassNotFound exception and returns Surface.of[java.lang.Object] so that it will not stop user programs.

But as we hit the class loader issue like sbt/sbt#5410 and #918 this behavior makes difficult to identify what happened behind the scenes, so we should be able to report ClassNotFoundException later.

Another approac

Description

There is no documentation describing the usage of the plugin with Kotlin DSL for Gradle

When trying a solution proposed in #127 I am getting an error:

* What went wrong:
Script compilation errors:

  Line 57:   testlogger {
             ^ Unresolved reference: testlogger

  Line 58:     theme = ThemeTy