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
Make flags local to the commands that actually support them. (#607)
Previously, many of the flags were global, instead of local to each
command. As a result, it was possible to set flags that are unsupported
for a given command.
This change makes all flags local, and only adds flags that are
actually supported by each command.
This improves the output of gopherjs --help and gopherjs <command>
--help, because it more accurately maps to the reality of flags and how
they're used. This way, flags that are unused by a certain command do
not show up in that command's --help output.
It's no longer possible to set -w flag with gopherjs serve, which was
meaningless (it had no effect, and was confusing).
The -w flag is also removed from gopherjs get command. It's unlikely
anyone is using -w flag together with gopherjs get command on purpose,
since it's pretty loaded and confusing. Instead, people can use
gopherjs get, followed by gopherjs install -w to achieve same effect.
Fixes#606.
verbose:=cmdTest.Flags().BoolP("verbose", "v", false, "Log all tests as they are run. Also print all text from Log and Logf calls even if the test succeeds.")
317
311
compileOnly:=cmdTest.Flags().BoolP("compileonly", "c", false, "Compile the test binary to pkg.test.js but do not run it (where pkg is the last element of the package's import path). The file name can be changed with the -o flag.")
318
312
outputFilename:=cmdTest.Flags().StringP("output", "o", "", "Compile the test binary to the named file. The test still runs (unless -c is specified).")
0 commit comments