Pretty much a summary of what it took process to run. From that record/information is where from that final message duct outputs should be rendered via f-string formatting pretty much. I.e. for
and we should add CLI option --report-format (`DUCT_REPORT_FORMAT) or alike so people could tune to their desires.
NB I know that exit code is not changing colors etc, but for that we might want to adopt/provide custom formatting similarly to how we do in pyout... later or add some ad-hoc for now exit_code_ansi_color and ansi_color_reset to use in the format as {exit_code_ansi_color}Exit code: {exit_code}{ansi_color_reset} but exclude them from record dumped to .json
Pretty much a summary of what it took process to run. From that record/information is where from that final message
duct
outputs should be rendered via f-string formatting pretty much. I.e. forShould be
and we should add CLI option
--report-format
(`DUCT_REPORT_FORMAT) or alike so people could tune to their desires.NB I know that exit code is not changing colors etc, but for that we might want to adopt/provide custom formatting similarly to how we do in
pyout
... later or add some ad-hoc for nowexit_code_ansi_color
andansi_color_reset
to use in the format as{exit_code_ansi_color}Exit code: {exit_code}{ansi_color_reset}
but exclude them from record dumped to .json