Offset 'extension' does not exist on array when using

[chrisrollins65]

Bug report

I have the following lines of code:

$pathInfo = pathinfo($filePath);
$extension = empty($pathInfo['extension']) ? '' : '.' . $pathInfo['extension'];

This results in the error PHPStan error:

Offset 'extension' does not exist on array('dirname' => string, 'basename' => string, 'filename' => string, ?'extension' => string).

I understand that the extension may not exist, but since this code explicitly checks that it does exist, I don't understand why this error is still appearing in PHPStan.
Is this a problem with PHPStan or do I need to change something else in my code?

Code snippet that reproduces the problem

https://phpstan.org/r/cf79be4b-a83a-4a68-b8ff-8fdf8e8ed49f

[mergeable]

This bug report is missing a link to reproduction on phpstan.org.
It will most likely be closed after manual review.

[amq]

@chrisrollins65 this should work:

$extension = array_key_exists('extension', $pathInfo) ? '.' . $pathInfo['extension'] : '';

[chrisrollins65]

@amq yes, but empty should work as well. I can use array_key_exists to get around this issue in this case, but it is still an issue nonetheless. empty also has the advantage of ensuring that this array element has a value, which array_key_exists and isset do not do.

[Progi1984]

@chrisrollins65 Another example : https://phpstan.org/r/53d3160d-0b51-4bb8-add1-e49aecc78458

[phpstan-bot]

@chrisrollins65 After the latest commit in dev-master, PHPStan now reports different result with your code snippet:

@@ @@
-9: Offset 'extension' does not exist on array('dirname' => string, 'basename' => string, 'filename' => string, ?'extension' => string).
+No errors

[phpstan-bot]

@Progi1984 After the latest commit in dev-master, PHPStan now reports different result with your code snippet:

@@ @@
-28: Offset 'id_customer' does not exist on array()|array(?'id_country' => int, ?'id_customer' => int).
+No errors

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.