Skip to content
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

✨ pkg/log/zap: clarify zap level vs. logr verbosity #1485

Merged
merged 1 commit into from Apr 21, 2021

Conversation

estroz
Copy link
Contributor

@estroz estroz commented Apr 19, 2021

This PR clarifies zap level vs. logr verbosity with a link to the zapr explanation of this difference, and test cases.

/kind documentation

Signed-off-by: Eric Stroczynski ericstroczynski@gmail.com

@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Apr 19, 2021
@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Apr 19, 2021
// Level sets the the minimum enabled logging level e.g Debug, Info
// See Options.Level
// Level sets Options.Level, which configures the the minimum enabled logging level e.g Debug, Info.
// If using zapcore.Level(N), where N > 0, set zapcore.Level(-1*N) instead.
Copy link
Contributor

Choose a reason for hiding this comment

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

This line feels confusing, I think you mean the second bit to be Level(-1*N) for how to call this function? Or the first?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Lmk if my update makes more sense.

Copy link
Contributor

Choose a reason for hiding this comment

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

👍 Clearer!

Copy link

@kensipe kensipe left a comment

Choose a reason for hiding this comment

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

agree with coderanger... this line is hard to parse... otherwise lgtm

…xplanation and test cases

Signed-off-by: Eric Stroczynski <ericstroczynski@gmail.com>
@estroz
Copy link
Contributor Author

estroz commented Apr 19, 2021

/test pull-controller-runtime-test-master

@coderanger
Copy link
Contributor

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 19, 2021
Copy link
Member

@alvaroaleman alvaroaleman left a comment

Choose a reason for hiding this comment

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

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alvaroaleman, estroz, kensipe

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 21, 2021
@k8s-ci-robot k8s-ci-robot merged commit 1c186f5 into kubernetes-sigs:master Apr 21, 2021
@k8s-ci-robot k8s-ci-robot added this to the v0.9.x milestone Apr 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/documentation Categorizes issue or PR as related to documentation. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants