You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use baseline reportUnmatched for both method_exists outcomes
PHPStan analyzes against the single installed OptionsResolver version on
each CI job, so the method_exists() guard appears tautological as either
"always true" (>= 7.3 on PHP 8.2+) or "always false" (< 7.3 on PHP 7.4-
8.1) with different identifiers per outcome. Inline @PHPStan-Ignore
treats every listed identifier as required, so the non-firing one trips
reportUnmatchedIgnoredErrors.
Use the baseline form with reportUnmatched: false on both entries, so
whichever fires gets silenced and the other entry quietly does nothing.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
# The method_exists(setOptions) guard supports symfony/options-resolver versions both
22
+
# with and without the method. PHPStan resolves against the installed version on each
23
+
# CI job, so exactly one of these two outcomes fires per job; reportUnmatched silences
24
+
# the other.
25
+
-
26
+
rawMessage:"Call to function method_exists() with Symfony\\Component\\OptionsResolver\\OptionsResolver and 'setOptions' will always evaluate to true."
27
+
identifier:function.alreadyNarrowedType
28
+
reportUnmatched:false
29
+
path:lib/Tmdb/Client.php
30
+
31
+
-
32
+
rawMessage:"Call to function method_exists() with Symfony\\Component\\OptionsResolver\\OptionsResolver and 'setOptions' will always evaluate to false."
0 commit comments