Support tool list --output-format=json#13962
Support tool list --output-format=json#13962InSyncWithFoo wants to merge 20 commits intoastral-sh:mainfrom
tool list --output-format=json#13962Conversation
CodSpeed Performance ReportMerging #13962 will not alter performanceComparing Summary
|
|
Thanks for your patience here. I'm planning to do a pass on this to make it consistent with #13689 unless you're interested? In particular, I think we should:
|
|
@zanieb I'm occupied at the moment, so please, go ahead and thanks. |
|
Is there still interest in this PR? Would be a great feature to have ❤️ |
|
@zanieb @InSyncWithFoo I just ran into a situation where this would have been useful. Would it be okay if I took a stab at this in the coming weeks? No guarantees, but I have the itch and I might have time. Specifically, I'm thinking of doing 2 PRs, one that would refactor the reporting stuff from project sync off on its own, and a second which implements |
|
Feel free yeah! I haven't had a chance to pick it up. cc @EliteTK |
Summary
Resolves #13633.
tool list --output-format=jsonoutputs information about the installed tools in JSON. An example output looks like this:[ { "name": "black", "version": "24.2.0", "version_specifiers": ["==24.2.0"], "extra_requirements": [], "with_requirements": [], "directory": "[...]/tools/black", "environment": { "python": "[...]/tools/black/bin/python3", "version": "3.12.1" }, "entrypoints": [ { "name": "black", "path": "[...]/bin/black" }, { "name": "blackd", "path": "[...]/bin/blackd" } ] } ]--show-paths,--show-version-specifiers,--show-withand--show-extrasare allowed to be used with--output-format, but they are redundant; the output will always include those information.Test Plan
Unit tests.