logstage: handling of optional arguments

Would it make sense to handle optional arguments like this:

val name = Option("myName")
val age = Option.empty[Int]
izLogger.info(s"$name $age")

currently prints name=Some(myName) age=None how about having it just print name=myName

My usecase is a rate-logger with an optional “total” argument, so the log looks either like:

• no known total: rate=8/s done=14
• with known total: rate=8/s done=14 left=238 donePercent=5%

[pshirshov]

I think this should be implemented at rendering policy level.

For json policy this can be achieved by customising circe’s Printer (there is an option to skip nulls), for string policy we may add a parameter for this.

Also there is an argument flag to suppress argument names, we may add one more flag (or turn existing one into an ADT) so we may adjust None/null suppression at for each individual argument.

[neko-kai]

@an-tex Definitely feel free to pursue this! Although do try to make it configurable as not everyone might want such behavior by default.