It would be nice if Arcade had some utility functions in PowerShell and bash that help format error messages and warnings in the explicit Pipelines way. Then utility scripts in various repos could just call, for example
Write-PipelineError "The system is down."
And get that translated into
##vso[task.logissue type=error]this is an error
if the script is running in a Pipelines environment, and just red text otherwise.
Probably with additional optional arguments for the sourcepath, linenumber, columnnumber, and code fields.
(Related to #2036 but would be helpful independently of the full flow back to GitHub, since these errors are displayed better on Pipelines build-result pages.)
It would be nice if Arcade had some utility functions in PowerShell and bash that help format error messages and warnings in the explicit Pipelines way. Then utility scripts in various repos could just call, for example
And get that translated into
if the script is running in a Pipelines environment, and just red text otherwise.
Probably with additional optional arguments for the
sourcepath,linenumber,columnnumber, andcodefields.(Related to #2036 but would be helpful independently of the full flow back to GitHub, since these errors are displayed better on Pipelines build-result pages.)