- Issue created by @jay jangid
- @jay-jangid opened merge request.
- Issue was unassigned.
- Status changed to Needs review
almost 2 years ago 1:02pm 1 February 2023 - Status changed to Closed: won't fix
almost 2 years ago 5:47pm 21 February 2023 - 🇧🇪Belgium RandalV
Frankly, this is not okay.
This is the so-manieth issue I've seen from either you or one of your colleagues that is just entirely wrongly done and I refuse to spend any more time fixing these MRs.Obviously this was done through phpcbf, but you're quite literally removing all of the specifically descriptive comments and replacing them with "Summary of ..." as well as the return types when they're not specifically typehinted, see the image attached for one example out of tens or even hundreds.
How is that an improvement?To be blunt, if you're going to try and farm "credited on ... fixed issues", please, at least do it in a manner that is helpful.
I'm going to close this issue as "won't fix". If you wish to actually fix the MR, I'll commit it.
For future reference: simply running phpcs & phpcbf is not the solution. Phpcbf is merely a tool that could reduce the amount of repeated work you perform but you simply cannot let it replace existing descriptive comments with something vague like "Summary of ...", and remove half of the @return statements simply because it's not specifically typehinted.
You can run phpcbf on a file, but if the result of phpcbf is not up to standards you yourself still need to fix that.