simplyadmire/composer-plugins

This package is abandoned and no longer maintained. No replacement package was suggested.

Composer plugin for installing PHP_CodeSniffer standards

Maintainers

Details

github.com/SimplyAdmire/ComposerPlugins

Source

Issues

Wiki

Installs: 509 305

Dependents: 5

Suggesters: 0

Security: 0

Stars: 15

Watchers: 4

Forks: 9

Open Issues: 3

Type:composer-plugin

2.1.0 2016-05-12 11:58 UTC

Requires

LGPL-3.0+ d8380f670694c1c2330b22591ca74adc82cffe19

  • Rens Admiraal <rens.woop@simplyadmire.com>

standardsTYPO3 FlowTYPO3 Neosphpcstypo3PHP_CodeSnifferTYPO3 CMS

This package is auto-updated.

Last update: 2022-02-01 12:27:42 UTC

README

A collection of composer plugins for specific installation instruction for composer packages.

Important: if you are running on Flow 3+ and have the typo3/ci-flow package installed using your main distributions composer.json you should remove it there and install the codesniffer in a separate folder, like for example: https://git.typo3.org/Neos/Distributions/Base.git/tree/refs/heads/master:/Build/PhpCodesniffer

PHP Codesniffer Standard installer

The PHP Codesniffer Standard installer is able to install phpcs codesniffer standards into the <vendor>/squizlabs/php_codesniffer/CodeSniffer/Standards/ folder. By doing so the standard will be usable by calling bin/phpcs --standard <standard>.

How To Use

  • Find the package containing the codesniffs you want to use. This package should be a normal Codesniffing package containing a ruleset.xml and a composer.json.
  • The composer package type has to be phpcodesniffer-standard
  • The name of the package has to reflect the name of the standard (explained below)
  • It's best if the package has a requirement to simplyadmire/composer-plugins. This is the only way to be sure the installer is available before the package is installed.
  • Now add the package as a development dependency to your project
  • Run bin/phpcs -i and see your standard listed

Naming Rules

The name of the standard is derived from the composer packagekey. The part after the / is taken as standard name. The first character is made uppercase, and all characters after a - will be uppercased. So:

  • vendor/mysniffs becomes Mysniffs
  • vendor/some-more-words becomes SomeMoreWords

TYPO3 Specific

The TYPO3 community already has packages available on packagist, and as renaming packagenames would be a bad practice we added 3 hardcoded standard names. Also the vendor name TYPO3 will always be enforced to be uppercase.

To include the TYPO3 CGL to your project you can use one of the following commands (depending on the CGL you want to use, TYPO3 Flow or TYPO3 CMS):

TYPO3 Flow:

	composer require --dev typo3-ci/typo3flow=dev-master

TYPO3 CMS:

	composer require --dev typo3-ci/typo3cms=dev-master

Now you can sniff your packages with for example:

	bin/phpcs --extensions=php --standard=TYPO3Flow Packages/Application/My.Package