-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add filtering to logger #15212
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changes looks good, we'll need to wait till rs/zerolog#527 is merged to exclude the replace directive from go.mod file
bdace30
to
2362d56
Compare
failing tests |
Yes, due to #15261 (comment). However I am not removing it here as this PR touches only |
log/logger.go
Outdated
// TODO wait for https://github.com/rs/zerolog/pull/527 to be merged | ||
// keys := e.GetKeys() | ||
keys := []string{} | ||
keys, err := e.GetKeys() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we make this method a function that takes keys until the pr is merged? Thinking how we can get this merged
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unfortunately, this isn't possible. We have no way to access the log keys from the hook.
I can re-comment this line, and when the zerolog PR is merged we can uncomment it.
That works too for me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
awesome lets do it, we can block v1 of logger till then and only release v0.1 for now
Description
Closes: #14967, follow-up of #15011
ref: rs/zerolog#527
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change