From 55101fd5093b11dbb06d60459ea10d59bc83ec13 Mon Sep 17 00:00:00 2001 From: jrfnl Date: Sun, 12 Nov 2023 22:34:29 +0100 Subject: [PATCH] Sod it --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 20d2b200..6008a279 100644 --- a/README.md +++ b/README.md @@ -164,11 +164,11 @@ For things to continue working when you add PHPCSUtils to your standard, you nee To support non-Composer based installs for running your sniff unit tests, you will need to adjust the PHPUnit `bootstrap.php` file to allow for passing an environment variable pointing to your PHPCSUtils installation.
- Example bootstrap code using a PHPCSUTILS_DIR environment variable + Example bootstrap code using a PHPCSUtils_DIR environment variable ```php // Get the PHPCS dir from an environment variable. -$phpcsUtilDir = getenv('PHPCSUTILS_DIR'); +$phpcsUtilDir = getenv('PHPCSUtils_DIR'); // This may be a Composer install. if ($phpcsUtilDir === false && file_exists(__DIR__ . '/vendor/autoload.php')) { @@ -191,7 +191,7 @@ if ($phpcsUtilDir === false && file_exists(__DIR__ . '/vendor/autoload.php')) { echo 'Uh oh... can\'t find PHPCSUtils. If you use Composer, please run `composer install`. -Otherwise, make sure you set a `PHPCSUTILS_DIR` environment variable in your phpunit.xml file +Otherwise, make sure you set a `PHPCSUtils_DIR` environment variable in your phpunit.xml file pointing to the PHPCS directory. '; @@ -208,7 +208,7 @@ Once that's done, you will need to make a small tweak to your own dev environmen ```xml - + ```