- Issue created by @bhaveshdas
- Status changed to Needs review
9 months ago 11:30am 21 March 2024 - š®š³India bhaveshdas
hello,
fixed all issue.
But still there are one issues left.
could you please review it.FILE: /var/www/html/drupal-contri-d10/modules/contrib/captchetat/css/captchetat.css ----------------------------------------------------------------------------------- FOUND 1 ERROR AFFECTING 1 LINE ----------------------------------------------------------------------------------- 1 | ERROR | [x] Expected 1 newline at end of file; 0 found ----------------------------------------------------------------------------------- PHPCBF CAN FIX THE 1 MARKED SNIFF VIOLATIONS AUTOMATICALLY ----------------------------------------------------------------------------------- Time: 216ms; Memory: 12MB
- šµšPhilippines clarkssquared
Hi
I applied patch #2 and I confirmed that it fixes all the PHPCS issues.
ā google_translator git:(master) ā curl https://www.drupal.org/files/issues/2024-03-21/3432640-2.patch | patch -p1 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 1300 100 1300 0 0 2119 0 --:--:-- --:--:-- --:--:-- 2145 patching file google_translator.info.yml patching file 'js/disclaimer.js' ā google_translator git:(master) ā .. ā contrib git:(master) ā phpcs --standard=Drupal,DrupalPractice --extensions=php,module,inc,install,test,profile,theme,css,info,txt,md,yml google_translator ā contrib git:(master) ā
RTBC +1 from me.
- Status changed to Closed: works as designed
9 months ago 5:30pm 23 March 2024 - šŗšøUnited States jenna.tollerson Atlanta, Georgia, USA
Thank you for your report.
The warnings reported in google_translator.info.yml do not exist in the git source; they are being added to your code by drupal.org packaging. This is working as intended.
There is no javascript support in the Drupal standards for phpcs. It was removed some time ago. ā Because you specified 'js' as one of the extensions to be evaluated, phpcs is treating it as if it was PHP. However, changing 'true' to 'TRUE' would break the javascript. I suggest pulling the correct list of extensions to evaluate from the coder README: https://github.com/pfrenssen/coder#usage