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
@ [ " ", Subtext "<", Punctuation String.concat "." message.name, Subtext ">", Punctuation ]
in literateDefaultTokeniser.
literateDefaultTokeniser
The text was updated successfully, but these errors were encountered:
Are we talking about Logary proper here?
In the Facade, we can change the outputTemplate to include the {source} value:
outputTemplate
{source}
let loggerTemplate = LiterateFormatting.tokeniserForOutputTemplate "[{level}] {timestampUtc:u} {message} [{source}]{exceptions}" let singleLetterLogLevel = function Verbose->"V" |Debug->"D" |Info->"I" |Warn->"W" |Error->"E" |Fatal->"F" let loggerOptions = { Literate.LiterateOptions.create() with getLogLevelText = singleLetterLogLevel } let logger = LiterateConsoleTarget([|"Suave";"Example"|], Debug, options=loggerOptions, literateTokeniser=loggerTemplate) :> Logger
Sorry, something went wrong.
I wonder if now would be a good time to add a similar feature to Logary proper?
Nice, that would be good to put in the docs; I ended up modifying the default tokeniser in the Facade, like you'll see in the commits.
Feature parity is always a good idea :)
efb55b2
No branches or pull requests
in
literateDefaultTokeniser
.The text was updated successfully, but these errors were encountered: