refactor: replace explicit log level constants with iota #481
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
armineyvazi
force-pushed
the
refactor/use-iota-for-log-levels
branch
2 times, most recently
from
4c4b9c9 to
f89766a
Compare
armineyvazi
force-pushed
the
refactor/use-iota-for-log-levels
branch
from
f89766a to
85a916c
Compare
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.
This change replaces the explicit integer assignments for log level constants (INFO, DEBUG, TRACE) with Go's idiomatic iota. This improves code readability and reduces potential errors when adding new levels in the future.