Add baseline for strict comparison php code sniffer rule#2739
Merged
Crabcyborg merged 2 commits intoJan 8, 2026
Conversation
Crabcyborg
deleted the
add_baseline_for_strict_comparison_php_code_sniffer_rule
branch
January 8, 2026 16:59
stephywells
pushed a commit
that referenced
this pull request
Apr 4, 2026
…arison_php_code_sniffer_rule Add baseline for strict comparison php code sniffer rule
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This enforces that we use
===instead of==.For now I'm just ignoring the problem files. We want to fix these soon.
But this makes sure that it's checked automatically in new pull requests in any other files that don't already have issues.