Open hrb90 opened 6 years ago
Sounds worse than using jq .set psc-package.json
though
Sure, that works too, but it assumes that (1) you have jq
installed and know how to use it, and (2) you already know that the package set is defined in the top-level "set" field of psc-package.json
, which isn't obvious to new users.
What are the downsides to printing the package set in available
?
I generally don't want to break anyone who wants to use existing output for sourcing information. This should end up being a separate command if someone really wants it, but otherwise we should close the issue.
It'd be nice if you could see what package set you're using from the CLI, instead of having to tab into your editor or
cat
your psc-package.json. I figure either we could have aset
command that just prints the set, or we could put it at the top ofavailable
.