Closed jimmymcpeter closed 5 months ago
Hi @jimmymcpeter thanks for opening the issue!
Have you tried using batch (--batch
or -B
) option with the phrase cli? It should provide just that - parsable output without any warnings. (Of course, it's possible that it doesn't cover all possible places where phrase cli has output, please point us to particular use cases and we're address them.)
Hope this helps. We're address the setup-cli
issue separately.
Have you tried using batch (--batch or -B) option with the phrase cli?
I wasn't aware of this -- Thank you!
I'd love a way to consistently obtain JSON output from the CLI. npm does this with the json config on various commands. Below are a few examples of where I've encountered difficulty relying on the CLI output:
If my CLI is not the latest version, the output includes an update notification printed after every phrase command I run.
If a request takes too long, the connection gets cut and your CDN returns a 504 along with HTML content. Your backend API server still processes the request.
I think just a way to turn off the update notification would be a nice option for now. I use this in GitHub Actions with the setup-cli action which requires the exact version be set (It doesn't support SemVer notation like actions/setup-node does) so I don't have an easy way to use the latest.