This meta issue is the parent for all coding-standards and best practice issues for Scheduler 8.x-1.x.
Core 9.5
PHP_codeSniffer 3.7.1, Coder 8.3.15 - 0 messages
Core 10.05
PHP_codeSniffer 3.7.1, Coder 8.3.16 - 0 messages
Correct as at 23 June 2023.
Before posting to this issue please check the current branch test results via https://www.drupal.org/node/3292/qa to confirm that there are coding standards faults that need to be fixed.
To run a coding standards check, the best way is to navigate into the scheduler folder, then just run phpcs
cd path/to/modules/scheduler
phpcs .
or from further up the folder hierarchy you need to specify the --standard parameter
phpcs path/to/modules/scheduler --standard=path/to/modules/scheduler/phpcs.xml.dist
If there is a problem, create a child issue to deal with it, as this is a [meta] issue and should not contain any patches or merge request branches.
| Comment | File | Size | Author |
|---|
Issue fork scheduler-3176822
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
jonathan1055 commentedAt Core 9.2 with new Coder release 8.3.11 we have 11 new coding standards warnings
https://www.drupal.org/pift-ci-job/1921382
Comment #4
jonathan1055 commentedThe previous coding standards issue is #2861902: Fix coding standards violations in 8.x codebase
Fixed the 10
@todocoding standards faults.Comment #7
jonathan1055 commentedComment #10
Nisha.Jain commentedHi, I have checked the coding standard issues.I found 3 errors.
Moving status needs to work.
Comment #11
Nisha.Jain commentedHi,
I have created the patch and solved the issues.Please review it.
Comment #12
himanshu_jhaloya commentedHi @Nisha.jain i am reviewing your patch
Comment #13
himanshu_jhaloya commentedHi @Nisha.jain i reviewed your patch. It is applied cleanly
Comment #14
himanshu_jhaloya commentedComment #15
jonathan1055 commentedHello Nisha.Jain and himanshu_jhaloya,
Thanks for your interest in Scheduler. However there are no coding standards faults that need to be fixed. Take a look at the test output that runs on Drupal.org https://www.drupal.org/pift-ci-job/2457718 - you will see that it is clean.
The problems you see are because you are running a plain phpcs, whereas you should be using the scheduler phpcs.xml file configuration
There are some customisations for coding standards, such as increasing the allowed array line length and allowing a blank line after a comment. If you run with that option you will see that your messages are not shown.
Actually, you should be able to leave out the
--standardoption, because Schedulers phpcs.xml.dist file will be used by default if it exists.Also, please note that when you see an issue with a title that starts with [meta] it means that the issue is created for the purpose of collecting several related issues together and for discussing the bigger picture. There should be no branch forks or patches add to this issue.
Thanks
Jonathan
Comment #16
arti_parmar commented**
Comment #17
jonathan1055 commented@arti_parmar what you have done is very unhelpful. You have erased the existing issue summary and replaced it with 100s of lines of coding standards output which is useless. Please read the comment #15 immediately above yours. You will notice that you are running the wrong command so that the project's phpcs.xml.dist file is not being used. Even if there were coding standards faults (which there aren't) pasting 100s of lines here makes the issue hard to use, you should link to a test output run on drupal.org. In fact if you looked at https://www.drupal.org/node/3292/qa you would see that there are no errors.
Messages such as the above imply to me that you are using the wrong set of coding standards sniffs.
Comment #18
arti_parmar commentedComment #19
jonathan1055 commentedRe-created the issue summary.
Comment #20
Neeraj333 commentedI have fixed the error on the scheduler. Please verify this.
Comment #21
jonathan1055 commented@Neeraj333 There are no coding standard errors on Scheduler 8.x-1.x. You have wasted your time. Please read the issue summary, and the above comments in #15 and #17.
Comment #22
Neeraj333 commented@jonathan1055 Yes but there were some coding standard errors so i fixed them. Thanks.
Comment #23
jonathan1055 commentedThere are no coding standard errors, you must be running the wrong command, read the comments above.
The branch test show it it clean https://www.drupal.org/pift-ci-job/2505954
Comment #24
rohit.rawat619 commentedFixing coding Standard
Comment #25
rohit.rawat619 commentedComment #27
jonathan1055 commentedRohitRawat676, there are no coding standards faults in Scheduler 8.x-1.x
I think you are not running the phpcs script correctly. You need to make sure the projects phpcs.xml config file is being used.
See https://www.drupal.org/project/scheduler#standards
Comment #28
jonathan1055 commentedUpdated issue summary, now that 8.x-1.x also runs on D10
Comment #29
jonathan1055 commentedEverything is fixed, at 8.x-1.x and 2.x so we no longer need this meta issue.
Individual new issues can be raised when coding standards are updated and new warning reported.