aboutsummaryrefslogtreecommitdiffstats
path: root/util/schemaspy
diff options
context:
space:
mode:
authorHarald Eilertsen <haraldei@anduin.net>2024-11-12 09:42:11 +0100
committerHarald Eilertsen <haraldei@anduin.net>2024-11-12 09:42:11 +0100
commit28b5b0cab5eeaecaa4cb2b4f765c1d0d354550e4 (patch)
tree3a4eb20931a780ee34bb4523387b01a07380f115 /util/schemaspy
parentce9d67f7b17a3b8c6dde40bce83e4329d1e7cdc2 (diff)
downloadvolse-hubzilla-28b5b0cab5eeaecaa4cb2b4f765c1d0d354550e4.tar.gz
volse-hubzilla-28b5b0cab5eeaecaa4cb2b4f765c1d0d354550e4.tar.bz2
volse-hubzilla-28b5b0cab5eeaecaa4cb2b4f765c1d0d354550e4.zip
Add PHPStan as a developer dependency.
PHPStan is a static PHP code analyzer that's aimed at finding actual bugs in the code. Where PHP Code Sniffer is about codeing standards, PHPStan is about correctness of code. The provided configuration file (`phpstan.neon.dist`) is configured to use the _lowest_ level of checks that PHPStan will report on. See https://phpstan.org/user-guide/rule-levels for information about the various rule levels. Run an analysis of the code base like this: % ./vendor/bin/phpstan It will output any found issues to stdout. You can also run it like this: % ./vendor/bin/phpstan --error-format=raw > phpstan.log This will give you an output file in a format that's suitable for use with typical editors for mapping errors to source locations.
Diffstat (limited to 'util/schemaspy')
0 files changed, 0 insertions, 0 deletions