Don't recognize object method as filesystem func

[bug-tape]

If you have a class with a method e.g. delete this sniff will give a warning when used with dynamic parameter. As long as only global functions must be checked this makes no sense.

[jmarcil]

Congratulations, you have found a false positive bug that goes way beyond your proposed fix!

For instance, what happens if you name your class method encrypt ? You'll get a warning. Actually this is the case for anything that is return by any $utils::get*Functions() , so it goes beyond FilesystemFunctionsSniff.

And here's the other use case not covered: ::. You could have a method call to your class with that such as $a::delete($a); and in this case get the same false positive.

I'll merge and fix.

Also, this skip will require ParanoiaMode off as it to remove a false positive.

In the future I think this is relevant enough so that we could patch other sniffers as well (like my encrypt example above).

Thanks!

[bug-tape]

You're absolutely right. I only fixed the case that was bugging me.
Thanks for merging.

[igoooor]

Sorry to come back 2 years later, I'm only discovering this tool now.
I am facing the same issue with a custom class having a delete method and resulting in WARNING | Filesystem function delete() detected with dynamic parameter
According to this merged PR, this should not happen right?
Am I missing something?

I am using the latest version and running the following command:

phpcs --runtime-set ParanoiaMode 0 --ignore=Kernel.php --standard=Security ./