This repository has been archived by the owner on Sep 18, 2019. It is now read-only.
Don't create extra flag namespaces for embedded fields #7
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Similar to how endoding/json handles embedded structs. This is also how
BurntSushi/toml handles them so it makes sense to have corresponding
flag names.
Sorry for the noise in tests, had to rename existing
embedded
tonested
to avoid confusion.