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

Make output consistent for each command when there is a problem with the command's parameters #2075

Closed
eppeters opened this issue Dec 1, 2015 · 3 comments

Comments

@eppeters
Copy link
Contributor

eppeters commented Dec 1, 2015

Issue #2066 was addressed by PR #2074, which determined that it would be best to default to displaying a help screen to the user when bower search is run with incorrect (no) parameters. For instance, if no package parameter is passed to bower info, it should default to showing the output of the bower help info command.

Currently the command just exits without a message if run without a package param. The situation is similar for the commands info, home, lookup, update, uninstall, and unregister.

bower register currently displays an error message with usage when run with no parameters, but this could instead use the help screen to be consistent and change according to the bower help register screen's updates.

@heinst
Copy link
Member

heinst commented Dec 7, 2015

Ill help out with this one...already got info done Ill do a few then create a PR

@eppeters
Copy link
Contributor Author

eppeters commented Dec 7, 2015

Nice! Be sure to check out #2074 because it should now be very easy to make a command default to the help screen. You just need to throw the right error in the readOptions for the command. Ignore me if you already knew that :P

@leegee
Copy link

leegee commented Apr 1, 2016

# cd to a directory with no `bower.json` present
$ bower install
bower                           ENOENT No bower.json present
$ bower update

lee@DESKTOP-LTN5CQN MINGW64 /d/src/thin-monitor2/test/e2e (protractor-cucumber)
$

benmann added a commit that referenced this issue Apr 28, 2016
info message added for bower register
Closing #2075
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants