- Nov 25, 2024
-
-
Mario authored
-
- Nov 22, 2024
-
-
Mario authored
-
-
- Nov 21, 2024
- Nov 19, 2024
-
-
Mario authored
(cherry picked from commit c6269854) Co-authored-by: Saiwal K <sk@utsukta.org>
-
Harald Eilertsen authored
-
- Nov 18, 2024
-
-
Mario authored
-
- Nov 17, 2024
- Nov 16, 2024
-
-
Harald Eilertsen authored
-
- Nov 14, 2024
- Nov 13, 2024
- Nov 12, 2024
-
-
Harald Eilertsen authored
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.
-
- Nov 11, 2024
-
-
Mario authored
-
Mario authored
(cherry picked from commit 8268ed1b) Co-authored-by: Mario <mario@mariovavti.com>
-
Mario authored
-
Harald Eilertsen authored
Thought this should have been part of the change set that turned the DB_Update routine to a static function instead of a constructor to an object that is not used.
-
Mario authored
-
- Nov 10, 2024
-
-
Mario authored
-
Mario authored
-
Mario authored
-
Mario authored
-
Harald Eilertsen authored
This also allows us to deduplicate initialization and validation.
-
Harald Eilertsen authored
These seem to be entirely independent, so moving the body of the if statements to separate functions should be fine.
-
Mario authored
-