From 61744dcbaae1c28adcdc7438b47e53e5ca11d929 Mon Sep 17 00:00:00 2001 From: Ian Dunn Date: Wed, 27 Apr 2022 13:30:24 -0700 Subject: [PATCH] Tools: Rename lint/format scripts to match newer repos. --- README.md | 7 ++++--- composer.json | 4 ++-- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 1caa025..aceb458 100644 --- a/README.md +++ b/README.md @@ -46,9 +46,10 @@ If you are making changes to the plugins, you can run `composer update` at `/wp- And lastly, you can run PHPCS for both the theme and the plugin at the root `/wp-content/` folder by running `composer install` there once, followed by `composer run phpcs` when you want to code scan. -* `composer run phpcs` - Lint the entire codebase -* `composer run phpcs -- -a themes/wporg-5ftf/` - Lint a specific folder, interactively -* `composer run phpcbf` - Fix linter warnings (when possible) +* `composer run lint` - Lint the entire codebase +* `composer run lint -- -a themes/wporg-5ftf/` - Lint a specific folder, interactively +* `composer run lint $(pwd)/inc*/ac*` - List file(s) in the current directory without typing the full path +* `composer run format` - Fix linter warnings (when possible) * `composer run test` - Run unit tests * `composer run test:watch` - Run unit tests after each file change. diff --git a/composer.json b/composer.json index 1190ef3..eca3fc5 100644 --- a/composer.json +++ b/composer.json @@ -23,10 +23,10 @@ "spatie/phpunit-watcher": "^1.23" }, "scripts": { - "phpcs": [ + "lint": [ "phpcs --extensions=php -s -p" ], - "phpcbf": [ + "format": [ "phpcbf -p" ], "test" : "phpunit",