phpyii2yii2-advanced-appphpcsphp-cs-fixer

How to check the parse or syntax error in Yii2 code Standard?


I have used this phpcs.xml.dist to check for code standard:

<?xml version="1.0" encoding="UTF-8"?>
<ruleset name="Yii2">
    <description>Yii 2 Web Application Framework Coding Standard</description>

    <rule ref="PSR2">
        <!-- Property names MUST start with an initial underscore if they are private. -->
        <exclude name="PSR2.Classes.PropertyDeclaration.Underscore"/>

        <!-- Opening parenthesis of a multi-line function call must be the last content on the line. -->
        <!-- Closing parenthesis of a multi-line function call must be on a line by itself. -->
        <!-- Only one argument is allowed per line in a multi-line function call. -->
        <exclude name="PEAR.Functions.FunctionCallSignature"/>

        <!-- We don't have line length (line width) limits. -->
        <exclude name="Generic.Files.LineLength"/>

        <!-- CASE keyword must be indented 4 spaces from SWITCH keyword. -->
        <exclude name="PSR2.ControlStructures.SwitchDeclaration"/>
    </rule>

    <!-- Property declaration rules. -->
    <!-- TODO: -->

    <!-- Function call signature. -->
    <!-- TODO: -->

    <!-- Switch declaration. -->
    <!-- TODO: -->

    <!-- ... other Yii2 specific rules. -->
    <rule ref="Generic.Arrays.DisallowLongArraySyntax"/>

    <!-- If string doesn't contain variables or single quotes, use single quotes. -->
    <rule ref="Squiz.Strings.DoubleQuoteUsage.NotRequired"/>

    <!-- Replaces Yii2_Sniffs_Files_SpacesAroundConcatSniff -->
    <rule ref="Squiz.Strings.ConcatenationSpacing">
        <properties>
            <property name="spacing" value="1" />
            <property name="ignoreNewlines" value="true" />
        </properties>
    </rule>

    <!-- Replaces Yii2_Sniffs_Properties_PrivatePropertiesUnderscoreSniff -->
    <rule ref="Squiz.NamingConventions.ValidVariableName.PrivateNoUnderscore"/>

    <!-- https://github.com/squizlabs/PHP_CodeSniffer/issues/1008 -->
    <rule ref="Squiz.ControlStructures.ControlSignature">
        <properties>
            <property name="requiredSpacesBeforeColon" value="0" />
        </properties>
    </rule>

    <!-- Ignore for migrations. -->
    <!-- Ignore missing namespace for migrations -->
    <rule ref="PSR1.Classes.ClassDeclaration.MissingNamespace">
        <exclude-pattern>m\d{6}_\d{6}_.+\.php$</exclude-pattern>
    </rule>
    <!-- Ignore camel caps format for class name of migrations -->
    <rule ref="Squiz.Classes.ValidClassName.NotCamelCaps">
        <exclude-pattern>m\d{6}_\d{6}_.+\.php$</exclude-pattern>
    </rule>

    <!-- Ignore for tests. -->
    <!-- Ignore method name prefixed with underscore to indicate visibility -->
    <rule ref="PSR2.Methods.MethodDeclaration.Underscore">
        <exclude-pattern>tests?/*(Cest|Test).php$</exclude-pattern>
    </rule>
    <!-- Ignore declare new symbols and execute logic with side effects same file -->
    <rule ref="PSR1.Files.SideEffects.FoundWithSymbols">
        <exclude-pattern>/tests?*/_bootstrap.php$</exclude-pattern>
        <exclude-pattern>/web/(index|index-test).php$</exclude-pattern>
    </rule>
<rule ref="Generic.Files.LineLength">
     <properties>
         <property name="lineLimit" value="120" />
         <property name="absoluteLineLimit" value="120" />
     </properties>
 </rule>
    <exclude-pattern>*/i18n/data/*</exclude-pattern>
    <exclude-pattern>*/views/errorHandler/*</exclude-pattern>
    <exclude-pattern>*/requirements/*</exclude-pattern>

 <exclude-pattern>ProfileTarget.php</exclude-pattern>
</ruleset>

The command I am using for it is:

vendor/bin/phpcs --encoding=utf-8 --extensions=php backend --colors

The file is in root directory. How can I use it to check for parse or syntax errors? It shows error for formatting, string error and other rules included in this file.

I can use this command to check the parse error for the single file:

php -l backend/controllers/AdvertisementController.php

I want to check the whole folder for any syntax or parse errors.


Solution

  • For syntax errors, there is the PHP linter. You can call it from within PHPCS by adding the Generic.PHP.Syntax sniff to your (custom) ruleset.

    Add the below in your phpcs.xml.dist.

    <rule ref="Generic.PHP.Syntax"/>