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

Sync Upstream #3

Open
wants to merge 50 commits into
base: master
Choose a base branch
from
Open

Sync Upstream #3

wants to merge 50 commits into from

Conversation

davecgh
Copy link
Member

@davecgh davecgh commented May 6, 2016

No description provided.

zimmski and others added 30 commits December 28, 2014 16:32
test IniParser.WriteFile with no-ini option
Updating the go get path for vet and cover
Add tests for negative numeric values using --long=value format
This adds a choice:”value” tag that can be specified multiple times
and limits the valid values of an option to a specific set.

Fixes jessevdk#147.
This behavior can be overridden by installing a custom completion handler
jessevdk and others added 20 commits October 18, 2015 18:29
You can now specify `required:"$n"` for rest arguments
…w/pre-Go 1.6)

Pre-Go 1.6, the newly added TestEmbeddedUnexported test passes. In Go
1.6beta1, it fails:

```
$ go test
--- FAIL: TestEmbedded (0.00s)
        assert_test.go:92: Unexpected parse error: unknown flag `v'
```

This commit makes the behavior consistent across Go versions.

Related: golang/go#12367, specifically the
comments about how "code that assumes `f.PkgPath != nil` means a field
is unexported and must be ignored must now be revised to check for
`f.PkgPath != nil && !f.Anonymous` for it to walk into the embedded
structs to look for exported fields contained within."
…rted-fields

Parse unexported embedded option struct fields in Go 1.6 (consistent w/pre-Go 1.6)
Simplifies the mental mapping of CLI flag name to INI config property
name.

See jessevdk#157 for more
information.
ini: allow specifying group opts directly on subcommands
This patch tweaks the behavior of --help so that positional arguments
that don't have a description are not listed. This allows certain
applications, that include a separate description of what each
positional argument does, to suppress otherwise duplicated help entry.

Signed-off-by: Zygmunt Krynicki <[email protected]>
Don't display description-less positional args in --help
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

Successfully merging this pull request may close these issues.