You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The package has moved to a new organisation - see #146.
For consistency and predictability as well as not to confuse people less familiar with the history of the project, I'd like to propose updating the namespace.
I'm undecided on what the new namespace should be.
The other projects in the PHPCSStandards organisation do not use the PHPCSStandards namespace prefix, they mostly use a project name based prefix, though this is largely due to the namespace rules from PHPCS having to be respected for those projects.
Open question:
Are there any namespace name rules for Composer plugins which should be followed ?
If not, just swopping out the DealerDirect prefix in favour of PHPCSStandards seems the most straight-forward way to action this.
The text was updated successfully, but these errors were encountered:
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 with the history of the project, I'd like to propose updating the namespace.
I'm undecided on what the new namespace should be.
The other projects in the
PHPCSStandards
organisation do not use thePHPCSStandards
namespace prefix, they mostly use a project name based prefix, though this is largely due to the namespace rules from PHPCS having to be respected for those projects.Open question:
If not, just swopping out the
DealerDirect
prefix in favour ofPHPCSStandards
seems the most straight-forward way to action this.The text was updated successfully, but these errors were encountered: