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
I prefer to use <issueHandlers> in Psalm config instead of using the tool-specific @psalm-suppress annotation, but it seems there is no way to limit these only to specific functions or methods.
Some issue types support this via <referencedMethod>, <referencedClass> or <referencedVariable>, but most of them don't.
Maybe something like <method> and <function> could be implemented for all issue types?
<issueHandlers>
<SomeIssue>
<errorLeveltype="suppress">
<!-- suppress SomeIssue, but only inside the code or doc-blocks of these methods or functions -->
<methodname="Example\SomeClass::someMethod" />
<functionname="Example\someFunction" />
</errorLevel>
</SomeIssue>
</issueHandlers>
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello.
I prefer to use
<issueHandlers>
in Psalm config instead of using the tool-specific@psalm-suppress
annotation, but it seems there is no way to limit these only to specific functions or methods.Some issue types support this via
<referencedMethod>
,<referencedClass>
or<referencedVariable>
, but most of them don't.Maybe something like
<method>
and<function>
could be implemented for all issue types?What do you think?
Beta Was this translation helpful? Give feedback.
All reactions