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 logs are printed on the command line via println. Replacing all the logs with tracing::info! and tracing::debug! would give flexibility with where we show the output - terminal, log file, or upload to a telemetry service using open telemetry.
It is also possible to pipe the stdout and stderr of rysnc and gradlew, so we can choose to filter it out (without relevant command line argument).
Thoughts?
The text was updated successfully, but these errors were encountered:
Currently all the logs that Mainframer prints are expected to be seen by user
Perhaps we could add --quiet flag that might rely on something like tracing to suppress the output.
With regards to logging into a log file or uploads to telemetry servers — this is not needed as Mainfraimer is a CLI tool for users, not a backend service or something like this I'd say :)
Currently logs are printed on the command line via
println
. Replacing all the logs withtracing::info!
andtracing::debug!
would give flexibility with where we show the output - terminal, log file, or upload to a telemetry service using open telemetry.It is also possible to pipe the
stdout
andstderr
ofrysnc
andgradlew
, so we can choose to filter it out (without relevant command line argument).Thoughts?
The text was updated successfully, but these errors were encountered: