Updated config reference docs generation #160
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
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #160 +/- ##
==========================================
- Coverage 52.78% 52.51% -0.27%
==========================================
Files 53 53
Lines 3698 3717 +19
==========================================
Hits 1952 1952
- Misses 1626 1645 +19
Partials 120 120 ☔ View full report in Codecov by Sentry. |
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.
Description
Changed (and bugfixed) the configdoc script.
Type of change
Changes
durationfresh->durationFresh,dryrun->dryRun). The naming implementation was copied from the JSON schema generator's naming function.Motivation
The tabwriter makes it more readable, and the naming fixes makes it match up with the JSON schema.
Viper (the config library) doesn't care about casing in YAML fields, so using all lowercase still works