DataTypeNamespace complains about namespace when PHPStan types are used

Thanks for reporting!

Can you put a full code example where the problem triggers in the issue summary?

I tried to reproduce with this, but works fine for me:

use Foo\Bar\Testi;

/**
 * Example.
 *
 * @phpstan-type UserAddress array{street: string, city: string, zip: string}
 */
class Test {

  /**
   * Address in the form of an array, defined on the class comment.
   *
   * @var UserAddress
   */
  protected $address;

  /**
   * Getter.
   *
   * @return UserAddress
   *   The address.
   */
  public function getAddress(): array {
    /** @var UserAddress $otherAddress */
    $otherAddress = [new Testi()];
    return $this->address;
  }

}

What am I doing wrong?

Side note: Coder cannot check if classes exist. It is coding standards checker that cannot access/process other PHP files to check if classes exist. We are deliberately leaving that to PHPStan.

As far as I understand our DataTypeNamespaceSniff it only checks that if a type matches the use statement, then the FQN should be used.

I have just came across the same issue and the example from #4 proves the problem.

In addition

 * @template Foo of \Drupal\foo\Bar
....
   * @phpstan-param Foo $apiBaseUrl

Foo in @phpstan-param also gets changed to FQCN.

This was fixed in Coder 9 and the sniff DataTypeNamespace removed.

Please test and let me know if this is still an issue!

Note that we are also dropping FQN checks in data type comments in #3360163: Stop using FQCN in @param @var @return annotations, that should land soon.

It still is an issue: #3607093: DataTypeNamespace complains about namespace when PHPStan types are *imported* using `@phpstan-import-type` then used — and I have a theory! 🤓