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
PHP Notice: Undefined index: V000 in phar:///path/php-semver-checker-git.phar/vendor/tomzx/php-semver-checker/src/PHPSemVerChecker/Configuration/LevelMapping.php on line 81
It appears that it is currently possible to trigger an Unknown. This operation can only trigger when analyzing a function.
I regularly test laravel's branches for semantic versioning changes and it appears to have been triggered by either laravel/framework@5699f63 or laravel/framework@cd56ae3. I will do some further analysis to determine which of the two is causing the problem as well as figure out why it is returning an Unknown operation.
Edit: Error is due to laravel/framework@5699f63. Basically, if nothing has changed, except for the comments, then it is "unknown". The php doc block is considered part of the Function_ object generated by PHP-Parser.
The text was updated successfully, but these errors were encountered:
Do not add an Unknown operation to reports. If we do not know what has changed, there is no reason to report it. A report should only contain changes we can explain.
It appears that it is currently possible to trigger an
Unknown
. This operation can only trigger when analyzing a function.I regularly test laravel's branches for semantic versioning changes and it appears to have been triggered by either laravel/framework@5699f63 or laravel/framework@cd56ae3. I will do some further analysis to determine which of the two is causing the problem as well as figure out why it is returning an
Unknown
operation.Edit: Error is due to laravel/framework@5699f63. Basically, if nothing has changed, except for the comments, then it is "unknown". The php doc block is considered part of the
Function_
object generated by PHP-Parser.The text was updated successfully, but these errors were encountered: