gubler / var-dump-finder-task
This package is abandoned and no longer maintained.
No replacement package was suggested.
Finds instances of var_dump() in your source code.
v0.1
2016-03-02 17:15 UTC
Requires
- php: ^5.5|^7.0
- phing/phing: ^2.8.0
Requires (Dev)
- phpdocumentor/phpdocumentor: ^2.8
- phpunit/php-code-coverage: ^2.1.0
- phpunit/phpunit: ^4.8
- squizlabs/php_codesniffer: ^2.3
This package is auto-updated.
Last update: 2021-06-17 19:52:00 UTC
README
Phing tasks to check for var_dump()
usage in
your source code. This is helpful as part of precommit checks to make
sure you don't commit debug code into your repository.
Installation
Install this package through Composer:
composer.phar require gubler/var-dump-finder-task
Setup
You can import the task into your build:
<import file="./vendor/gubler/var-dump-finder-task/task.xml"/>
Or define the vardumpfinder
task in your build.xml
file:
<taskdef name="vardumpfinder" classname="Gubler\Phing\VarDumpFinderTask\VarDumpFinderTask" />
Usage
VarDumpFinderTask has two attributes and requires a <fileset>
of files to check.
Attributes
Name | Type | Description | Default |
---|---|---|---|
haltonmatch | Boolean | halt and fail the build if match found | false |
findincomments | Boolean | find uses of var_dump in comments | false |
Example
<vardumpfinder haltonmatch="true" findincomments="true" > <fileset /> </vardumpfinder>
License
gubler/var-dump-finder-task is released under the MIT license.