Vscode-intelephense: Add config to enable/disable diagnostics

[bmewburn]

[nunoperalta]

I would love to have this implemented!

I get several "Expected type 'int'. Found 'string'." that I would like to disable.

Every other check is welcome.

[bmewburn]

@nunoperalta could you add a code snippet so I can reproduce this? I want to minimise false positives too.

[nunoperalta]

function get_date(_int_ $unix_timestamp) { }

$result = mysqli_query('SELECT time FROM table');
$row = mysqli_fetch_assoc($result);
echo get_date(_$row['time']_);

Expected type 'int'. Found 'string'.
intelephense(10006)

Note that I do want all other errors in relation to type issues. I just want to be able to ignore the specific "expected int / found string" ones.

[LorenzoRamalho]

+1 for this feature. All of the fatal errors I currently have are of this kind, and I use type juggling on purpose so this becomes quite an annoying false positive. I wouldn't mind it being a warning though.
But I've only experienced this with int and strings. When expecting more complex objects like classes things could get complicated.

[bmewburn]

Diagnostics can be disabled completely or categories of diagnostics disabled in 1.3. Expected type 'int'. Found 'string' was due to declare(strict_types=1) always assumed to be set, in 1.3 files are inspected for this declaration and type checking adjusted accordingly.

[jpike88]

Why don't a comment just be added above the affected line, just like how ts-ignore works in Typescript? I don't want to disable an entire type of check just because of one line.

My use case: A lambda function. There's supposed to be a function 'lambda' which I shouldn't be declaring.

[mahatma-andy]

Why don't a comment just be added above the affected line, just like how ts-ignore works in Typescript? I don't want to disable an entire type of check just because of one line.

Seconded. My use case is a PHPUnit test where an invalid value is intentionally given to test the correct exception is thrown.

[bmewburn]

This is tracked in #568