Consider changing Composer package type to "phpcodesniffer-standard"

[rodrigoprimo]

This PR suggests changing the Composer package type to enable automatic standard registration via the PHPCSStandards Composer installer plugin.

Problem/Motivation

Composer allows declaring a package's type. This package currently uses "library" as its type.

There is a Composer plugin that can install custom PHP_CodeSniffer standards: https://github.com/PHPCSStandards/composer-installer

This plugin is part of the PHPCSStandards organisation, which is the new official home of PHP_CodeSniffer.

For this installer to work, the package type needs to be set to phpcodesniffer-standard.

There are already over 470 packages that use this type. As a side benefit, using this type will allow end-users to more easily find other external PHP_CodeSniffer standards that may be interesting to them when searching on Packagist.

Proposed changes

Change the type in composer.json from "library" to "phpcodesniffer-standard".

This will in no way change the existing behavior of this package for users that do not include the Composer plugin mentioned above in their projects' composer.json.

[DanielEScherzer]

Thanks!

[DanielEScherzer]

Do I need to make a new release in order for this to become useful/live?

[rodrigoprimo]

Yes, a new release would be needed for this change to take effect for users that require a stable version of the package.

Packagist has already picked up the change on dev-main, so users requiring "dev-main" would already get the updated package type. But for anyone using a tagged release, the type in the currently published versions (v0.0.1 and v0.0.2) is still "library".