composer-installer
composer-installer copied to clipboard
Composer installer for PHP_CodeSniffer coding standards
## Problem/Motivation My github action is terminating with an error. My [github action](https://github.com/kathyisawesome/wc-not-sold-separately/blob/trunk/.github/workflows/release.yml#L40-L68) is calling `composer install` ``` - name: "Install Composer dependencies with development dependencies." run: | composer install...
I'd like to re-open the discussion around whether the paths registered with PHPCS should be absolute or relative paths. Some previous issues related to this: #14, #33, #73 ### Current...
This ticket is meant as the next iteration, following up on #91 In this iteration, the following additional variants should be explored: - [x] Having some builds with a global...
At this moment, the plugin very deliberately only registers packages with the `phpcodesniffer-standard` type set in their `composer.json` file with PHP_CodeSniffer (providing a `ruleset.xml` file can be found in the...
Follow up on #113 and #146, which contain mentions/discussions about this as well. Now the repository has moved to the PHPCSStandards organisation and been renamed to `composer-installer`, the question arises...
In a way a "bit late to the party", but should the default branch be renamed away from `master` ? And if so, what would be the preferred new name...
## Problem/Motivation The plugin updates the `installed_paths` when the installed dependencies have changed or the search depth has changed. However, when the `phpcodesniffer-search-depth` is _removed_ and the `Dealerdirect\Composer\Plugin\Installers\PHPCodeSniffer\Plugin::run()` method is...
## Problem/Motivation My CI jobs are occasionally failing with the below error ## Expected behaviour No fatal error ## Actual behaviour ``` Fatal error: Uncaught Error: Cannot call constructor in...
With all of the hard work, changes and improvements over the last year (or two), we have reached a point where we can confidently say that this project has matured...
Previously mentioned in comments in #159 The package has moved to a new organisation - see #146. For consistency and predictability as well as not to confuse people less familiar...