Add Values() #167
Merged
Add Values() #167
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a Values() option, as well as a NoComments flag.
Values() will return a slice of possible values (the actual enum type).
NoComments will remove the auto generated comments for the enum values. If you specify comments on your enums, then those will still live on, but the auto generated portion will not. This has been particularly annoying when using go-swagger to generate a swagger doc from the generated code... as it interprets each comment as part of the value, and you get a weird looking description in your api doc. This option allows for those to be optional given the use.
fixes #157