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
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.
The text was updated successfully, but these errors were encountered:
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
# 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)
$
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 nopackage
parameter is passed tobower info
, it should default to showing the output of thebower help info
command.Currently the command just exits without a message if run without a
package
param. The situation is similar for the commandsinfo
,home
,lookup
,update
,uninstall
, andunregister
.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 thebower help register
screen's updates.The text was updated successfully, but these errors were encountered: