refact: EventerType and improve consistency #24665
Merged
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.
In the original implementation in
libpod/events/config.go
,iota
was used to designEventerType
.However, in
libpod/events/events_freebsd.go
andlibpod/events/events_linux.go
, theNewEventer
function still relies on string comparisons to determine whichEventerType
to use.EventerType
comment.EventerType
to be represented as astring
.EventerType
is designed to be entirely lowercase, changed the comparison to use lowercase instead of uppercase.newEventJournalD
tonewJournalDEventer
, similar to the functionsnewLogFileEventer
andnewNullEventer
events_linux.go
.Does this PR introduce a user-facing change?