You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the library only outputs to the console via System.out -- great for simple debugging purposes in simple apps, but in the case of more complex apps that need to be profiled or watched for debugging or performance metrics (like web apps) it can make it harder than necessary to find and view the output that you want to view, especially if custom logging configurations are being used by the web app.
Would be handy if the library used a standard logging mechanism that in addition to giving simple output in simple cases, can be configured to output in more complex configurations.
The text was updated successfully, but these errors were encountered:
After doing a proof of concept using java.util.Logger, the logging output became a messy disaster to try and visually parse through for information.
I don't want to add an entire logging framework dependency like log4j or logback until users demand it.
Logging has been unified to the new log() method and supports string formatted messages with params for the time being but continue to print to System.out -- I imagine in most cases people can capture the output from their app server easily enough to view this.
Currently the library only outputs to the console via System.out -- great for simple debugging purposes in simple apps, but in the case of more complex apps that need to be profiled or watched for debugging or performance metrics (like web apps) it can make it harder than necessary to find and view the output that you want to view, especially if custom logging configurations are being used by the web app.
Would be handy if the library used a standard logging mechanism that in addition to giving simple output in simple cases, can be configured to output in more complex configurations.
The text was updated successfully, but these errors were encountered: