You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vendor/bin/phpstan analyze -c phpstan.neon.dist
355/355 [============================] 100%
------ ---------------------------------------------------------------------------------------------------------
Line N/A
------ ---------------------------------------------------------------------------------------------------------
-1 Out of 1295 possible param types, only 57 % actually have it. Add more param types to get over 99 %
-1 Out of 1582 possible return types, only 32 % actually have it. Add more return types to get over 99 %
-1 Out of 873 possible property types, only 0 % actually have it. Add more property types to get over 99 %
------ ---------------------------------------------------------------------------------------------------------
as you can see, in this case we get a error-line reported as -1 and a file of N/A.
I think for error messages which are not related to a file, the result table should not print out a line - as it doesn't make sense to print a line number, when no filename is known.
therefore I would prefer a result table like
vendor/bin/phpstan analyze -c phpstan.neon.dist
355/355 [============================] 100%
---------------------------------------------------------------------------------------------------------
Out of 1295 possible param types, only 57 % actually have it. Add more param types to get over 99 %
Out of 1582 possible return types, only 32 % actually have it. Add more return types to get over 99 %
Out of 873 possible property types, only 0 % actually have it. Add more property types to get over 99 %
---------------------------------------------------------------------------------------------------------
for this kind of errors
The text was updated successfully, but these errors were encountered:
Feature request
using collectors you often create error messages which are not tight to a specific file
e.g. as described in https://tomasvotruba.com/blog/how-to-measure-your-type-coverage/
you get a output of:
as you can see, in this case we get a error-line reported as
-1
and a file ofN/A
.I think for error messages which are not related to a file, the result table should not print out a line - as it doesn't make sense to print a line number, when no filename is known.
therefore I would prefer a result table like
for this kind of errors
The text was updated successfully, but these errors were encountered: