Php-language-server: Add config to disable comment warnings

[tungvn]

OS: Window 10
VS Code: 1.6.1

I get a lot of warnings about comment, like as "\No is not a valid Fqsen". Although it's our failed when we're not comment follow PHP common syntax, we should have a config to disable this warnings.

[bsienn]

I'm also having such error everywhere.

[felixfbecker]

@bsienn because * is not a valid FQSEN.

[bsienn]

@felixfbecker I think the DocComments should be excluded from FQSEN checking. Is there any workaround for this? I'm not much aware of this but vscode is complaining about these.

[felixfbecker]

@bsienn we need to parse doccomments for @param and @var declarations. And that comment is causing a parsing error, because it is invalid syntax. Warnings are ignored already for files inside vendor.

[scott-davidjones]

@felixfbecker i think there needs to be some kind of exclusion, my phpUnit annotations are being picked up:

/**
     * test that array is returned
     * 
     * @dataProvider dpRawData
     * @covers ::buildMultipleEntitiesByWorkId
     * @covers ::<private>
     */

these are perfectly correct according to PHPUnits documentation:
https://phpunit.de/manual/3.7/en/appendixes.annotations.html#appendixes.annotations.covers

whilst i understand that in PHP they are not correct they should still be allowed to be excluded.

[codycraven]

This is a problem all over Drupal's codebase:

  /**
   * Support for fstat().
   *
   * @return bool
   *   An array with file status, or FALSE in case of an error - see fstat()
   *   for a description of this array.
   *
   * @see http://php.net/manual/streamwrapper.stream-stat.php
   */

  /**
   * The Editor Plugin Manager.
   *
   * @var \Drupal\editor\Plugin\EditorManager;
   */

[LC43]

a flag would be nice to have. currently, with hundreds of php files, its impossible to use Problems Panel, which we use often with PHPCS.

It even complains about files that aren't opened in the editor.

With many shared codebases, we don't have control to fix the warnings, so these reports are not useful at all.

thanks,

[benignant]

I'm also having this issue. This warning is all over the place in third-party code (e.g. WordPress). An option to ignore this particular warning would be great.

[khoazero123]

you can comment this line (hello đồng hương :)))

[jens1o]

I would rather not do that.

[ee0pdt]

I've used @khoazero123's workaround for now, but I too would like a flag to toggle this warning

[felixfbecker]

Afaik the latest version doesn't show the warning.