Skip to content
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

View package set from CLI #101

Open
hrb90 opened this issue Apr 15, 2018 · 3 comments
Open

View package set from CLI #101

hrb90 opened this issue Apr 15, 2018 · 3 comments

Comments

@hrb90
Copy link

hrb90 commented Apr 15, 2018

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 a set command that just prints the set, or we could put it at the top of available.

@justinwoo
Copy link
Collaborator

Sounds worse than using jq .set psc-package.json though

@hrb90
Copy link
Author

hrb90 commented Apr 15, 2018

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?

Rembane pushed a commit to Rembane/psc-package that referenced this issue May 26, 2018
@justinwoo
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants