-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
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
Best practices for dealing with interfering log statements #214
Comments
I realize #99 might be a bit related, though I do not want to write to a file. |
I can see something like that being useful. On JVM at least, you can also redirect all of stdout through mordant: #171 (comment) |
Yeah, though a Mordant log appender which would allow you to redirect all log output e.g. to a Mordant table cell / panel would really be nice, I guess. |
A Mordant appender would be great |
I have an internal app framework that wraps Mordant and it does this. At some point I hope to be able to contribute some of this stuff upstream, but unfortunately I don't have a whole lot of time to work on it. The gist is:
|
I'm wondering whether there are and hints / best practices on how to deal with log statements from third-party libraries while displaying a
MultiProgressBarAnimation
on the console. Log output from third-part libraries causes lines being printed to the console that mess up Mordant's rendering of progress bars etc.As the log out is useful and should not be suppressed, would it maybe even make sense to have a Mordant-based log "appender" that can be used with common logging frameworks like Log4j or SLF4J to direct log output to a console are that Mordant "knows of" and thus does not mess with the progress bars?
The text was updated successfully, but these errors were encountered: