Skip to main content

php annotation type

Annotation to indicate the type of a variable

Static analysis tools are invaluable for catching errors and improving code quality. However, they sometimes struggle to infer the type of a variable, especially in complex scenarios. This can lead to false positives or missed errors. In this post, we'll explore how to use annotations to explicitly tell Intelephense (and other similar tools) the type of a variable in PHP, ensuring accurate static analysis.

The Problem: Intelephense's Limitations

Let's say we have a PHP controller method where we retrieve a user object:



class TestAuthController extends AbstractController
{
  #[Route('/api/test/auth', name: 'api_test_auth')]
  public function testAuth(): Response
  {
    $user = $this->getUser();
    
    if ($user) {
      return $this->json(
        [
          'id' => $user->getId(), 
          'username' => $user->getUserIdentifier(),
          'name' => $user->getFirstName() . ' ' . $user->getLastName(),
          'roles' => $user->getRoles()
        ]);
    }
    return $this->json(['message' => 'Not authenticated'], 401);
  }
}
    

Without knowing the type of "$user", Intelephense might flag "getId()", "getFirstName()", and "getLastName()" as unidentified methods, even if they exist on the actual "User" object. This is because the static analyzer can't definitively determine the type of "$user" based solely on the code.

The Solution: The "@var" Annotation

PHP's "@var" annotation provides a way to explicitly specify the type of a variable. This helps static analysis tools understand the code's intent and perform more accurate analysis. Since our "getUser()" method might return "null", we'll use a union type:


namespace App\Controller;

use Symfony\Component\HttpFoundation\Response;
use Symfony\Component\Routing\Annotation\Route;
use Symfony\Bundle\FrameworkBundle\Controller\AbstractController;


class TestAuthController extends AbstractController
{
  #[Route('/api/test/auth', name: 'api_test_auth')]
  public function testAuth(): Response
  {
    /** @var App\Entity\User|null $user */
    $user = $this->getUser();
    
    if ($user) {
      return $this->json(
        [
          'id' => $user->getId(), 
          'username' => $user->getUserIdentifier(),
          'name' => $user->getFirstName() . ' ' . $user->getLastName(),
          'roles' => $user->getRoles()
        ]);
    }
    return $this->json(['message' => 'Not authenticated'], 401);
  }
}
    

The code:/** @var App\Entity\User|null $user */ annotation tells Intelephense that "$use" is either an instance of "App\Entity\User" or "null". Now, Intelephense will correctly recognize the methods called on "$user" within the "if" block, eliminating the false positives.

By using "@var" annotations strategically, you can significantly improve the accuracy of your static analysis and catch potential errors before runtime.

Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='https://ngx.rktmb.org/foo' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href='https://ngx.rktmb.org/foo'" parameter. npm run build --base-href='https://ngx.rktmb.org/foo did not set the base href in indext.html After looking for a while, I found https://github.com/angular/angular-cli/issues/13560 where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='https://ngx.rktmb.org/foo...

wget maven ntlm proxy

How to make wget, curl and Maven download behind an NTLM Proxy Working on CentOS, behind an NTLM proxy: yum can deal without problem with a NTLM Proxy wget, curl and Maven cannot The solution is to use " cntlm ". " cntlm " is a NTLM client for proxies requiring NTLM authentication. How it works Install "cntlm" Configure "cntlm"  by giving it your credentials by giving it the NTLM Proxy Start "cntlm" deamon (it listens to "127.0.0.1:3128") Configure wget, curl and Maven to use "cntlm" instead of using directly the NTLM Proxy Note: You will have then a kind of 2 stages Proxy : cntlm + the NTLM proxy Configure CNTLM After installing cntlm, the configuration file is in "cntlm.conf". You must have your domain (in the Windows meaning), proxy login and  proxy password. Mine are respectively: rktmb.org, mihamina, 1234abcd (yes, just for the example) You must have you NTLM Proxy Hostnama or IP ...

VMWare Keyboard Latency

Workstation VM UI lag when typing When using a VMWare Workstation VM, I noticed there is a latency when typing in the keyboard and the real appearance of the typed character. I searched and found: Noticeable typing lag in Linux VM terminals since v16.2 upgrade on Linux host To make it short, what solved it for me: Disable 3D acceleration in the VM setting .