Fix LogDiagnosticsPlugin log target typo #18534
Merged
Conversation
This file contains 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
alice-i-cecile
approved these changes
Mar 25, 2025
alice-i-cecile
added
C-Bug
JaySpruce
approved these changes
Mar 28, 2025
JaySpruce
added
S-Ready-For-Final-Review
mockersf
pushed a commit
that referenced
this pull request
Mar 30, 2025
# Objective For the LogDiagnosticsPlugin, the log target is "bevy diagnostic" with a space; I think it may (?) be a typo intended to be "bevy_diagnostic" with an underline. I couldn't get filtering INFO level logs with work with this plugin, changing this seems to produce the expected behavior.
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.
Objective
For the LogDiagnosticsPlugin, the log target is "bevy diagnostic" with a space; I think it may (?) be a typo intended to be "bevy_diagnostic" with an underline.
I couldn't get filtering INFO level logs with work with this plugin, changing this seems to produce the expected behavior.