diff options
author | Harald Eilertsen <haraldei@anduin.net> | 2024-06-12 23:53:20 +0200 |
---|---|---|
committer | Harald Eilertsen <haraldei@anduin.net> | 2024-06-12 23:53:20 +0200 |
commit | 9199a1ba81b6ed2c6dcbc1f842eb31b5f2c7d919 (patch) | |
tree | 265ca47c9f2fda448b89f6dca9584017257d1ba7 /view/theme/diabook-aerith/fpostit/fpostit.php | |
parent | 9d56bb952e162dddd24d3bcdc50b2957ef0e0b97 (diff) | |
download | volse-hubzilla-9199a1ba81b6ed2c6dcbc1f842eb31b5f2c7d919.tar.gz volse-hubzilla-9199a1ba81b6ed2c6dcbc1f842eb31b5f2c7d919.tar.bz2 volse-hubzilla-9199a1ba81b6ed2c6dcbc1f842eb31b5f2c7d919.zip |
Add config file and rules for PHP Code Sniffer.
The rules are based on the "Generic" ruleset included by PHP Code
Sniffer, with a significant portion of the rules disabled. This is a
tradeoff between getting some useful feedback, and not being overloaded
by noise.
I've tried to encode a coe style that resembles the existing code as
much as possible, but have included some sniffs that requires code
changes to satisfy the style. This is meant as a starting point, and we
can disable or enable more sniffs as we see fit.
PHPCS also has ready rule sets for other common coding standards we may
want to gravitate towards, e.g. PSR-12. Others are available from the
community.
The best way to run PHPCS is to integrate it with your editor, so that
it will display diacnostics inline when saving or modifying the code. It
can also be run from the command line like this:
./vendor/bin/phpcs -n [<path-to-file-to-check>]
If no file is specified it will try to check the entire project.
The `-n` means don't bother with warnings (I recommend that to begin
with. Enable the warnings when the errors are taken care of.)
Diffstat (limited to 'view/theme/diabook-aerith/fpostit/fpostit.php')
0 files changed, 0 insertions, 0 deletions