New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commands returning data like --build_order sometimes get dirty output #1757
Comments
I think this was partially workarounded by #4359 as we now have the possibility of outputing a json file with the build order and avoid the stdout pollution. WDYT? |
This is related to #4055 . |
Glad I read this latest comment regarding future plans. Was about to write a script which depends on the json output to stdout. Is there a github issue open for any discussion about piping stdout to stdin between conan commands? There was an informal discussion in slack about it, and that would be an alternative to this kind of json parsing. |
To refresh your use case, Jerry, the main one was the conan reference from a create => to the conan upload command, right? |
Yes, that was the case that has come up the most. |
The whole terminal output has been changed, decoupled stdout for values, stderr for any other message and formatters to generate json or other formats. Already available in 2.0-alpha |
For example using version ranges:
$
conan info --build_order sdplog
Version range '>=4.0' required by 'None' resolved to 'fmt/4.0.0@xylosper/stable'
That message dirts the output and can be processed by an script.
Same problem with the warn we wanted to introduce when conan sets the runtime of visual automatically, we decided to log it.
Maybe these commands should specify a file or something?: There is already a json option to file
The text was updated successfully, but these errors were encountered: