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

Enhance and simplify logging guide #541

Closed
wants to merge 1 commit into from

Conversation

hpehl
Copy link
Contributor

@hpehl hpehl commented Feb 15, 2024

Fixes #540

@hpehl hpehl requested a review from jamezp February 15, 2024 09:12
@hpehl
Copy link
Contributor Author

hpehl commented Feb 15, 2024

@jamezp, any objections to merging this?

Copy link
Member

@jamezp jamezp left a comment

Choose a reason for hiding this comment

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

I actually see other things I'd like to change in here :) Would you prefer I make a PR to update this in general?

log.trace("called method with: " + name);
}

log.trace("called method with: {}", name);
Copy link
Member

Choose a reason for hiding this comment

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

This isn't quite correct. For a format like this it needs to be tracev. However, I'd suggest using:

log.tracef("called method: %s", name);

@hpehl
Copy link
Contributor Author

hpehl commented Feb 16, 2024

@jamezp I agree it's better you open a separate PR to adjust the content.

@jamezp jamezp mentioned this pull request Feb 16, 2024
@jamezp
Copy link
Member

jamezp commented Feb 16, 2024

@jamezp I agree it's better you open a separate PR to adjust the content.

Let me know what you think about #542 @hpehl. The plugin configuration could remove. However, it won't work out of the box the way that is currently shown. We might need a more uniform approach in general to that part of the message though.

@bstansberry
Copy link
Contributor

I've put the 'hold' label on this due to the discussion around #542. The label is just to make the fact there's an ongoing 'blocking' discussion more visible when looking at the PR queue.

@hpehl
Copy link
Contributor Author

hpehl commented Mar 19, 2024

@jamezp, I think we can close this PR now that #542 has been merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use SLF4J in logging guide
4 participants