This may take some work, however long term I think this is a good idea. I have looked through the Coder docs and I am not sure whether this functionality exists in an integrated form yet.

- Coder has a configuration file with a strict mode switch and with other switches for rule preferences that depart from strict mode.

- Projects that have had Coder applied to them also make available the Coder configuration file they are known to completely pass.

- Projects that pass Coder strict mode get a special indicator, say a Coder Strict icon, on their project home page.

This would enable people to depart from Drupal strict comment and coding standards in a controlled way, while still applying the majority of Coder rules.

Thus, I could say have a Coder configuration file that matches my own recipe for PHP that is more amenable to reverse engineering to UML, and does not apply rules such as this one: OO: Coder complains about camel caps (camelCase) argument to setter method in Class.

Projects hoping to move from the sandbox can, during application for full project rights, make available their Coder config file with the strict mode switch and other rule switches via the repository.

Comments

klausi’s picture

Status: Active » Closed (won't fix)

Coder 7.x is frozen now and will not receive updates. Coder 8.x-2.x can be used to check code for any Drupal version, Coder 8.x-2.x also supports the phpcbf command to automatically fix conding standard errors. Please check if this issue is still relevant and reopen against that version if necessary.