You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the output of each command is a human-readable table with no other options. This is fine for manual usage, but not for more complex scripting.
The WP-CLI has a notion of output formats, using the --format flag. It would be great if the Local CLI used a similar --format flag. Particularly, output in JSON would be parseable by scripts. I've already automated Local via this CLI and VS Code's Tasks feature. But those simple scripts are to turn on and off sites. To do anything more complex that relies on actually making logical decisions based on, say, if a site is running or not, my scripts would need to parse output from local-cli. Especially as more Local functionality gets exposed by this CLI, the output being friendly to scripting will be more and more useful.
The text was updated successfully, but these errors were encountered:
Currently the output of each command is a human-readable table with no other options. This is fine for manual usage, but not for more complex scripting.
The WP-CLI has a notion of output formats, using the
--format
flag. It would be great if the Local CLI used a similar--format
flag. Particularly, output in JSON would be parseable by scripts. I've already automated Local via this CLI and VS Code's Tasks feature. But those simple scripts are to turn on and off sites. To do anything more complex that relies on actually making logical decisions based on, say, if a site is running or not, my scripts would need to parse output fromlocal-cli
. Especially as more Local functionality gets exposed by this CLI, the output being friendly to scripting will be more and more useful.The text was updated successfully, but these errors were encountered: