Use cli fancy formatting again for build messages #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This resolves the issue previously seen in #19 where
output_file
wasn't found and that was caused by a confusedcli_process_start()
when called within a function but attached to a different environment (whereoutput_file
didn't exist).This fixes that particular issue by building the message first using
cli::format_inline()
before callingcli_process_start()
.While in there I also updated the printing method. I reversed the phrasing to Building input into output since I think this reads in chains better (the output of one line becomes the input of the next).
I also updated the messages to provide a little more context about where the files are being written by printing the paths relative to the working directory.