Composer: Add Commands

[n7studios]

Summary

Registers a number of commands in the scripts section of Composer, which serve as shorthand commands for testing and other common tasks performed in development, to save repetitively typing longer commands with commonly used flags / arguments.

Command	Description
phpcs	Runs PHP CodeSniffer on the entire plugin codebase
phpcs-tests	Runs PHP CodeSniffer specifically on the tests directory using test-specific standards
phpstan	Runs PHPStan static analysis with increased memory limit
test-integration	Builds and runs integration tests with fail-fast enabled

Adds alias commands:

Command	Description
coding-standards	Runs PHP CodeSniffer on the entire plugin codebase
fix-coding-standards	Runs PHP CodeSniffer specifically on the tests directory using test-specific standards
coding-standards-on-tests	Runs PHPStan static analysis with increased memory limit
fix-coding-standards-on-tests	Builds and runs end-to-end tests with fail-fast enabled
static-analysis	Builds and runs integration tests with fail-fast enabled

Commands can be run using e.g. composer test-integration or composer static-analysis

Testing

Existing tests pass

Checklist

• I have written a test and included it in this PR
• I have run all tests and they pass
• The code passes when running the PHP CodeSniffer
• Code meets WordPress Coding Standards for PHP, HTML, CSS and JS
• Security and Sanitization requirements have been followed
• I have assigned a reviewer or two to review this PR (if you're not sure who to assign, we can do this step for you)

[noelherrick]

You got me wondering if we should alias these with generalized names, like you did with "test-integration":

• run-coding-standards(-on-tests)
• run-beautifier(-on-tests)
• run-static-analysis

Thoughts?

[n7studios]

You got me wondering if we should alias these with generalized names, like you did with "test-integration":

• run-coding-standards(-on-tests)
• run-beautifier(-on-tests)
• run-static-analysis

Thoughts?

run- seems unnecessary, given all composer commands are running something (e.g. composer update is built in and updates the packages used for testing).

Command names match the underlying command where possible, to save developers guessing (e.g. composer phpcs runs vendor/bin/phpcs ./ -s -v), unless renaming makes it clearer (e.g. composer test runs both vendor/bin/codecept build @no_additional_args and vendor/bin/codecept run EndToEnd @additional_args --fail-fast).

For a full list of commands used in the Plugins, see the table in this PR. We don't have e.g. composer test here, as there are only integration tests for WordPress Libraries.

If you think there are improvements that can be made, let me know and I'm open to updating each Plugin to reflect this.

[noelherrick]

I suggested aliases because as someone who's not using these commands daily, I was vaguely aware that we had a linter/coding standards tool, didn't know we had a beautifier, and thought the PHPStan was the main automatic tool we were using. My thought was to add aliases as a way to document the different code tools.

[n7studios]

I suggested aliases because as someone who's not using these commands daily, I was vaguely aware that we had a linter/coding standards tool, didn't know we had a beautifier, and thought the PHPStan was the main automatic tool we were using. My thought was to add aliases as a way to document the different code tools.

These commands are already well documented, including what each one does. At a minimum, anyone not working in these repos daily should review that doc to understand what’s available and how to use it. As someone who does use them daily, I’d find it confusing if the commands suddenly changed.

That said, if you’d find aliases useful, let me know the list and I’ll add them. I don’t think it’s worth a lengthy back and forth beyond that, given the time cost.

Alias commands added. Original commands remain as faster to type and use for my development workflow.