This repository was archived by the owner on Sep 17, 2022. It is now read-only.
Correct form of a key in the reference #147
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dimitarvdimitrov
approved these changes
Sep 18, 2020
Collaborator
dimitarvdimitrov
left a comment
dimitarvdimitrov
left a comment
There was a problem hiding this comment.
Hi, thank you for handling this! 👍 I will release this by the end of the week.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Description
I was having trouble getting
keysOnlyto work, after staring at the examples for awhile I noticed that they usekeys_only— so I looked at the source and found that, yes, the YAML tag for this field iskeys_only. So I figured we should fix the reference.Type of change
Checklist:
Go code is formatted with(N/A)gofmtI have made corresponding changes to the docs in(N/A)/docsand in theREADMEI have added tests (unit and/or end-to-end) that prove my fix is effective or that my feature works(N/A)Any dependent changes have been merged and published (in downstream modules)(N/A)