improve phpdoc#5962
improve phpdoc#5962ColonelMoutarde wants to merge 23 commits intoFreshRSS:edgefrom ColonelMoutarde:chore/improve-phpdoc
Conversation
Take advantage of https://phpstan.org/blog/bring-your-exceptions-under-control Minimum changes to pass `tooWideThrowType` and `implicitThrows`. Revert some mistakes from: FreshRSS#5504 Preparation needed before new PRs of the same type: FreshRSS#5962 Fix several wrong PHPDocs and catches: > Method ... has ...Exception in PHPDoc @throws tag but it's not thrown. > Dead catch - ...Exception is never thrown in the try block.
|
Let's be a bit more methodic with #6037 first |
Take advantage of https://phpstan.org/blog/bring-your-exceptions-under-control Minimum changes to pass `tooWideThrowType` and `implicitThrows`. Revert some mistakes from: #5504 Preparation needed before new PRs of the same type: #5962 Fix several wrong PHPDocs and catches: > Method ... has ...Exception in PHPDoc @throws tag but it's not thrown. > Dead catch - ...Exception is never thrown in the try block.
|
Adding all the |
Co-authored-by: Alexandre Alapetite <alexandre@alapetite.fr>
|
To supplement my previous messages, I would like a more structured approach than random / partial changes in random files. For instance, taking one of the files modified with Setting to Line 42 in 7a9a24a this gives: Furthermore, some of those insights might indicate that we need to think how we handle exceptions in some cases. P.S.: 889 "errors" of this type in the whole project |
| $iMax = count($feedByCategory_calculated); | ||
| for ($i = 0; $i < $iMax; $i++) { |
There was a problem hiding this comment.
This does not correspond to the topic of the PR on improving PHPDoc (which was already quite vague).
I am not so found of PRs with various random changes, and prefer focussed PRs doing one thing well
Changes proposed in this pull request:
Pull request checklist: