Skip to content

feat: make the verbose option print loaded config values before merging#118

Open
Wafffle77 wants to merge 1 commit into
mainfrom
show-config-parameters
Open

feat: make the verbose option print loaded config values before merging#118
Wafffle77 wants to merge 1 commit into
mainfrom
show-config-parameters

Conversation

@Wafffle77

@Wafffle77 Wafffle77 commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

Checklist

  • My code follows the style guidelines of this project
  • I have added/updated comments where needed
  • I have added tests that prove my fix is effective or my feature works
  • I have run make test (or equivalent) locally and all tests pass
  • DCO Sign-off: All commits are signed off (git commit -s) with my real name and email
  • REUSE Compliance:
    • Each new/modified source file has SPDX copyright and license headers
    • Any non-commentable files include a <filename>.license sidecar
    • All referenced licenses are present in the LICENSES/ directory

Description

This PR makes the verbose option print the values it loaded from each config file before merging them, for debugging purposes.

Fixes #104

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

For more info, see Contributing Guidelines.

Signed-off-by: Ethan Clark <ethan.clark@trojans.dsu.edu>
@synackd synackd changed the title Make the verbose option print loaded config values before merging feat: make the verbose option print loaded config values before merging Jul 20, 2026

@synackd synackd left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, just a small change.

Also, would it be useful as a user to see the merged config in early verbose mode?

Comment thread internal/config/config.go
if err != nil {
return fmt.Errorf("failed to serialize config: %w", err)
}
log.EarlyLogger.BasicLogf("Config data: %s", serializedConfig)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we put a newline after Config data:? looks a bit awkward to have the first YAML key on the same line as the log message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature]: Show config file path and/or parameters in debug log messages

2 participants