-
-
Notifications
You must be signed in to change notification settings - Fork 4
Comments inside if statements are not parsed #111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
thanks for reporting. ATM we don't see all comments because of shortcommings on the phpstan end, see phpstan/phpstan#11701 (comment) hopefully we can address it in the future |
Thanks for your quick reply, and also the comment you linked - very interesting. Regarding the issue, luckily //todo comments inside if statements are very rare :) but let's hope improvements to the parsing will solve this issue at some point in the future |
note: the issue was about |
to get a more robust experience, I am thinking whether we should have a TodoBy attribute in addition to the current phpdoc syntax. a attribute would have the benefit that PHPStan can verify whether it was placed at a supported location and therefore you can't accidentally put the todo no a unsupported element. |
Hi there,
we are using your package to identify TODOs with expired dates. First of all, great package and thanks for making it!
Recently we added a
//todo 2024-09-10
inside an if statement and realized (after the deadline) that this was not picked up.Issue
Comments inside if statements are not parsed, therefore no rules are triggered.
Version
phpstan-todo-by 0.1.27
Example
If the comment is moved to on top of the if, it will be parsed:
The text was updated successfully, but these errors were encountered: