-
Notifications
You must be signed in to change notification settings - Fork 29
Add a config flags to standardize how we do things #2316
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
Draft
nolag
wants to merge
2
commits into
rtinianov_cre_psb_ms_1_capReg
Choose a base branch
from
rtinianov_cre_psb_ms_1_flags
base: rtinianov_cre_psb_ms_1_capReg
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| package configdoc | ||
|
|
||
| // LineKind classifies a line of a configuration document. | ||
| type LineKind int | ||
|
|
||
| const ( | ||
| // LineBlank is an empty or whitespace-only line, which terminates a comment block. | ||
| LineBlank LineKind = iota | ||
| // LineComment is a description line. | ||
| LineComment | ||
| // LineTable opens a table (section) of fields. | ||
| LineTable | ||
| // LineArrayOfTables opens a repeated table. | ||
| LineArrayOfTables | ||
| // LineField is a key/value pair. | ||
| LineField | ||
| ) | ||
|
|
||
| // Line is a parsed line: its kind, plus the piece of it that carries meaning - the comment | ||
| // text with its marker stripped, the table's name, or the field's key. | ||
| type Line struct { | ||
| Kind LineKind | ||
| Text string | ||
| } | ||
|
|
||
| // Format is a configuration file syntax. It both writes the pieces of a document (so callers | ||
| // can assemble one from Go structs) and recognizes them when reading one back (so a | ||
| // hand-written document can be turned into documentation). Implement it to document a format | ||
| // other than TOML; see TOML for the reference implementation. | ||
| type Format interface { | ||
| // Comment renders text as a description line. | ||
| Comment(text string) string | ||
| // Table renders the opening of a section, given its dotted path (e.g. "chain.nodes"). | ||
| Table(path string) string | ||
| // Field renders a key/value line. marker is DefaultMarker, ExampleMarker or | ||
| // DocsOnlyMarker, or empty for a plain value line with no documentation annotation. | ||
| Field(key, value, marker string) string | ||
| // Literal renders a Go value as a value literal of this format. | ||
| Literal(v any) string | ||
|
|
||
| // DefaultMarker annotates a field whose value is its real default. | ||
| DefaultMarker() string | ||
| // ExampleMarker annotates a field with no usable default, whose value is a placeholder. | ||
| ExampleMarker() string | ||
| // DocsOnlyMarker annotates a field that is documented but shown in no example. | ||
| DocsOnlyMarker() string | ||
|
|
||
| // ParseLine classifies one line of a document. | ||
| ParseLine(line string) Line | ||
|
|
||
| // Name returns the markdown name for code blocks | ||
| Name() string | ||
| } | ||
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What else did you have in mind? I thought we were leveraging TOMLs ease of parsing pretty directly here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From call: I'm worried about this being premature abstraction, but only because it is public API. If this is useful for readability besides, then keeping it internal and evolving until it is ready to be public would be fine.