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
{{ message }}
This repository has been archived by the owner on Apr 25, 2019. It is now read-only.
At present, the :msg and {:intent :msg ...} behavior is really magical and intended only for use by task implementers with specific behavior in mind. "logging" ala clojure.tools.logging sucks because people choose not to participate in it - eg depstar which sorta rolls its own structured logging using prn.
Really I need a reasonable composing pattern for capturing the *out* and *err* lines as well as other somewhat structured messages from tasks so that the :msg field can be automatically populated for tasks like compile which really have a lot to even without explicitly capturing and passing output to the user.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
At present, the
:msg
and{:intent :msg ...}
behavior is really magical and intended only for use by task implementers with specific behavior in mind. "logging" alaclojure.tools.logging
sucks because people choose not to participate in it - egdepstar
which sorta rolls its own structured logging usingprn
.Really I need a reasonable composing pattern for capturing the
*out*
and*err*
lines as well as other somewhat structured messages from tasks so that the:msg
field can be automatically populated for tasks likecompile
which really have a lot to even without explicitly capturing and passing output to the user.The text was updated successfully, but these errors were encountered: