Skip to content

fix: empty format in the config file should be treated as Default#448

Merged
theoludwig merged 2 commits intomainfrom
empty-format
Mar 15, 2025
Merged

fix: empty format in the config file should be treated as Default#448
theoludwig merged 2 commits intomainfrom
empty-format

Conversation

@klaernie
Copy link
Copy Markdown
Member

@klaernie klaernie commented Mar 3, 2025

Some of our users have an empty Format in their config file - this should be treated as having requested the "default" output format, as it would be when the option is missing entirely.

Closes #430

@klaernie klaernie force-pushed the empty-format branch 2 times, most recently from f296af0 to 8d8f800 Compare March 7, 2025 08:21
@theoludwig theoludwig requested a review from ccoVeille March 12, 2025 11:12
Copy link
Copy Markdown
Contributor

@ccoVeille ccoVeille left a comment

Choose a reason for hiding this comment

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

LGTM 👍

One suggestion anyway

Comment thread pkg/outputformat/outputformat.go Outdated
@klaernie
Copy link
Copy Markdown
Member Author

I would think this is good to merge now.

Some of our users have an empty Format in their config file - this
should be treated as having requested the "default" output format, as it
would be when the option is missing entirely.

Closes #430
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.

Empty Format field in config file breaks ECC

3 participants