FIX(core): @W-18539707@: Prevent logging rule override if it is the same value as default #295
Conversation
This file contains hidden or 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
…ame value as default
jfeingold35
approved these changes
May 16, 2025
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.
While looking at this forcedotcom/code-analyzer#1795 I noticed the users log file was flooded with messages like:
[2025-05-09T17:48:57.128Z] Debug Core - The severity value of rule 'ApexNullPointerException' of engine 'sfge' was overridden according to the specified configuration. The old value '3' was replaced with the new value '3'.
But the old value is the same as the new value... so we shouldn't be logging this.
This PR fixes this.