PhpStorm: code analysis - static calls from class name

Question

I have got a warning in PhpStorm for a common use of static calls. I have:

class Test {
  public static function thisIsATest(){
     // do stuff
  }
}

Then, I have:

$className = 'Test';
$className::thisIsATest();

This is not an error, btw I have this in my PhpStorm:

Is there a way to handle this? At least, is it possible to just hide this warning?

How about using PHP 5.3.0 or greater. Before this version, your syntax isnt allowed. Test Versions herer: sandbox.onlinephpfunctions.com — JustOnUnderMillions
– JustOnUnderMillions, Commented Jan 12, 2017 at 16:32
Alternative you can do this: call_user_func(array('Test','thisIsATest')); — JustOnUnderMillions
– JustOnUnderMillions, Commented Jan 12, 2017 at 16:36
Unfortunately PhpStorm does not support such class referencing properly yet. Two options 1) Disable "Unknown method" inspection .. but this will affect all other places as well; 2) Suppress message for this line by placing /** @noinspection PhpUndefinedMethodInspection */ on a line just before $className::thisIsATest(); 3) Give a hand to IDE by providing better type hint for $className variable -- the one that IDE understands: /** @var Test $className */ before $className = 'Test'; line — LazyOne
– LazyOne, Commented Jan 12, 2017 at 17:08
Disabling this inspection is not really an option. I hoped that there were a way to tell Phpstorm inspector how to handle this. Using /** @var ... is an option, but that bothers me because it's not its really type. — dam660
– dam660, Commented Jan 13, 2017 at 9:53
Afterwards, they introduced this syntax in php5.3 to avoid using call_user_func functions (as far as i know). I'm going to downgrade the severity of this warning for now. Thank's! — dam660
– dam660, Commented Jan 13, 2017 at 9:55

JustOnUnderMillions · Accepted Answer · 2017-01-13 15:36:33Z

2

There are some solutions, for this problem:

change to a PHP Version >= 5.3.0
use call_user_func(array('Test','thisIsATest')); in older PHP versions
change code-inspection-behavior in phpstrom under project settings (also ensure phpstrom has the right PhpVersion set up for your current project)
[Solution] Declare the variable with annotations in phpstrom in the right way!

Like:

  <?php
  /**
   * @var $className Test
   */
  $className::thisIsATest();

Now phpstrom know that $className is a instance of Test that has a method called thisIsATest, and no error hint pops up.

edited Jan 13, 2017 at 15:36

answered Jan 12, 2017 at 16:37

JustOnUnderMillions

3,80511 silver badges14 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

dam660 Over a year ago

In fact, my code works (i'm on a PHP5.6). It's just the code hilighter of Phpstorm which shows me a warning. I downgraded the severity for now. Thank's!

JustOnUnderMillions Over a year ago

@dam660 Working with Phpstorm feels sometimes like having a million minions around :-) I have noted a little bit late that your Q was about phpstrom not the code itself. :)

JustOnUnderMillions Over a year ago

@dam660 Check my answer again!

dam660 Over a year ago

Oh! This works! This syntax is not part of the documentation. It says : @var [“Type”] [$element_name] [<description>]. Your proposal is to switch $element_name with type. What does it really means? Thank you!

JustOnUnderMillions Over a year ago

@dam660 I some cases the second argument [$variablename] is optional, so maybe it also detects the first two arguments by itself, so the order isnt not really relevant. Also your link show the use within a class, but in my case it is used global. And in the end phpstorm does his interpretation. But, as long it worked ... :)

Collectives™ on Stack Overflow

PhpStorm: code analysis - static calls from class name

1 Answer 1

5 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

5 Comments

Your Answer

Sign up or log in

Post as a guest

Related