Separate yaml-handling and flag types out from flagutil.go #2068
Conversation
This file contains 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
This was referenced May 24, 2022
|
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
tempoz
force-pushed
the
flag-partition
branch
2 times, most recently
from
da51093
to
f9cf621
Compare
tempoz
changed the title
luluz66
approved these changes
Jun 14, 2022
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.
flagutil.gowas getting very large, and the yaml-handling was semanticallyvery different from modifying the flags directly or defining new flag types, so we
separate it out. We also take this opportunity to move the flag types to their own
file.
Version bump: Patch