Make WordPress Core


Ignore:
Timestamp:
08/17/2018 01:50:26 AM (6 years ago)
Author:
pento
Message:

Coding Standards: Upgrade WPCS to 1.0.0

WPCS 1.0.0 includes a bunch of new auto-fixers, which drops the number of coding standards issues across WordPress significantly. Prior to running the auto-fixers, there were 15,312 issues detected. With this commit, we now drop to 4,769 issues.

This change includes three notable additions:

  • Multiline function calls must now put each parameter on a new line.
  • Auto-formatting files is now part of the grunt precommit script.
  • Auto-fixable coding standards issues will now cause Travis failures.

Fixes #44600.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/wp-admin/about.php

    r43527 r43571  
    4141                            '&#x1F389'
    4242                        );
    43                     ?>
     43                        ?>
    4444                </h2>
    4545                <p><?php _e( 'Welcome to an improved Customizer workflow with design drafts, locking, scheduling, and preview links. What&#8217;s more, code syntax highlighting and error checking will make for a clean and smooth site building experience. Finally, if all that wasn&#8217;t pretty great, we&#8217;ve got a great new Gallery widget and improvements to theme browsing and switching.' ); ?></p>
     
    182182                        '&#x1F91D'
    183183                    );
    184                 ?>
     184                    ?>
    185185            </h2>
    186186            <p>
     
    191191                'https://github.com/WordPress/gutenberg'
    192192            );
    193                 ?>
     193            ?>
    194194                </p>
    195195        </div>
     
    205205                    '&#x1F60A'
    206206                );
    207             ?>
     207                ?>
    208208            </h2>
    209209
     
    218218                            'https://make.wordpress.org/core/2017/11/01/improvements-to-the-customize-js-api-in-4-9/'
    219219                        );
    220                     ?>
     220                        ?>
    221221                    </p>
    222222                </div>
Note: See TracChangeset for help on using the changeset viewer.