Skip to content

Consider changing Composer package type to "phpcodesniffer-standard"#41

Merged
tolik518 merged 1 commit intoflyeralarm:masterfrom
rodrigoprimo:fix/composer-type
Mar 16, 2026
Merged

Consider changing Composer package type to "phpcodesniffer-standard"#41
tolik518 merged 1 commit intoflyeralarm:masterfrom
rodrigoprimo:fix/composer-type

Conversation

@rodrigoprimo
Copy link
Copy Markdown
Contributor

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 "config" 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 "config" 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.

@tolik518
Copy link
Copy Markdown
Member

tolik518 commented Mar 14, 2026

Thank you for bringing this up!

Since it mainly improves compatibility with the PHPCSStandards Composer installer and does not change the behavior for users who do not use the plugin, it seems like a sensible adjustment!

@tolik518 tolik518 merged commit 6b6cef3 into flyeralarm:master Mar 16, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants