Skip to content

AC-206: Create UCT phpcs ruleset for customizations only #313

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

svera
Copy link
Contributor

@svera svera commented Oct 14, 2021

The new standard Magento2Framework and corresponding namespace containing tests applicable only for the framework testing are introduced.

The rules extracted to the new standard:

  • Magento2.Legacy.License
  • Magento2.Legacy.CopyrightAnotherExtensionsFiles
  • Magento2.Legacy.Copyright

jcuerdo
jcuerdo previously approved these changes Oct 14, 2021
loginesta
loginesta previously approved these changes Oct 18, 2021
@sivaschenko sivaschenko dismissed stale reviews from loginesta and jcuerdo via 655960e October 19, 2021 12:19
@@ -37,7 +37,8 @@ class RestrictedCodeSniff implements Sniff
*/
public function __construct()
{
$this->loadData('restricted_classes*.php');
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did create this method exactly to avoid the warning thrown by PHPCS about using include. But I guess it is OK to break our own rules sometimes :)

Copy link
Member

@sivaschenko sivaschenko Oct 19, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@svera the warning about include was skipped using phpcs:ignore (that is preserved, but the actual rule that needs to be skipped is specified after refactoring)

@svera
Copy link
Contributor Author

svera commented Oct 19, 2021

It is my own PR so I cannot approve it

@sivaschenko
Copy link
Member

@magento import pr to magento-commerce/magento-coding-standard

@m2-github-services
Copy link
Contributor

@sivaschenko an error occurred during the Pull Request import.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants