Add verbosity flag and fix annoying compiler warnings#47
Merged
Conversation
Fix compiler warnings, fix per https://elixirforum.com/t/changes-to-the-struct-update-syntax/71232
Owner
|
Thank you for the contribution! I'll see if I can release v0.11.1 with this change. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Not much to say. Add option_v with required loglevel. Maybe this should accept one of a few permitted options (error, warning, debug)? There's also all of the loglevel flags so better to keep as an open string for now.
Also fixed the struct update syntax warnings while I was there.
No AI was used in the making of this pull request.
Fixes #46, didn't realize how easy it would be until I started looking.