aboutsummaryrefslogtreecommitdiff
path: root/bool_func_test.go
diff options
context:
space:
mode:
authorGeorges Varouchas <[email protected]>2025-06-09 23:03:34 +0400
committerGeorges Varouchas <[email protected]>2025-06-09 23:03:47 +0400
commitf4c97c2487b06cff392d2958534e7195f79847fb (patch)
tree396084677a2d9f4b0303e46cb3c37324e3cd09ec /bool_func_test.go
parent8a6c85f2ae488081f953744f9edc414bac10ee45 (diff)
minor: fix typos in comments
Diffstat (limited to 'bool_func_test.go')
-rw-r--r--bool_func_test.go4
1 files changed, 2 insertions, 2 deletions
diff --git a/bool_func_test.go b/bool_func_test.go
index c81970a..ffb4fa9 100644
--- a/bool_func_test.go
+++ b/bool_func_test.go
@@ -75,7 +75,7 @@ func TestBoolFuncCompat(t *testing.T) {
args := []string{"--bflag", "--bflag=false", "--bflag=1", "--bflag=bar", "--bflag="}
// It turns out that, even though the function is called "BoolFunc",
- // the stanard flag package does not try to parse the value assigned to
+ // the standard flag package does not try to parse the value assigned to
// that cli flag as a boolean. The string provided on the command line is
// passed as is to the callback.
// e.g: with "--bflag=not_a_bool" on the command line, the FlagSet does not
@@ -106,7 +106,7 @@ func TestBoolFuncCompat(t *testing.T) {
flagName := "bflag"
args := []string{"--bflag", "--bflag=err", "--bflag=after"}
- // test behavior of standard flag.Fset with an error triggere by the callback:
+ // test behavior of standard flag.Fset with an error triggered by the callback:
// (note: as can be seen in 'runCase()', if the callback sees "err" as a value
// for the bool flag, it will return an error)
stdFSet := flag.NewFlagSet("std test", flag.ContinueOnError)