Skip to content
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

Migrate moodle-local_moodlecheck phpdoc checks to this standard #30

Open
19 of 24 tasks
andrewnicols opened this issue Sep 27, 2022 · 1 comment
Open
19 of 24 tasks

Comments

@andrewnicols
Copy link
Contributor

andrewnicols commented Sep 27, 2022

I think we can probably migrate most of our custom-written phpdoc checks into this standard.

There are several, but (un)helpfully phpcs sucks at documenting the rules available. Here's a summary of some of them:
https://stackoverflow.com/questions/13767550/is-there-a-phpcs-standard-targeting-php-docblocks

We will need to tailor this a little, but it should be able to capture most of the phpdoc sniffs for methods at the very least.

Forum discussion: https://moodle.org/mod/forum/discuss.php?d=455786

andrewnicols added a commit to andrewnicols/moodle-cs that referenced this issue Sep 27, 2022
This commit addss support for the standard Commenting sniffs relating
to methods only.

Some of the specific sniffs have been disabled, or their severity/type
changed to suit our rules.

Fixes moodlehq#30
@stronk7
Copy link
Member

stronk7 commented Feb 20, 2024

Just thinking... maybe we should comment about this plan also @:

Stating that, progressively, we are proceeding to migrate the current checks to moodle-cs and removing them from local_moodlecheck as we go?

So, some overlapping / dupe reports can be expected here and there (when releases adding and removing don't match) but, ultimately, removing local_moodlecheck from everywhere (CiBoT, moodle-plugin-ci, ...) once the transition is complete.

Ciao :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants