[wp-trac] [WordPress Trac] #50010: wp-includes/blocks shouldn't be excluded from coding standards

[WordPress Trac]

#50010: wp-includes/blocks shouldn't be excluded from coding standards
------------------------------------------+-------------------------------
 Reporter:  johnbillion                   |       Owner:  (none)
     Type:  task (blessed)                |      Status:  new
 Priority:  normal                        |   Milestone:  Future Release
Component:  Editor                        |     Version:  5.0
 Severity:  normal                        |  Resolution:
 Keywords:  good-first-bug needs-testing  |     Focuses:  coding-standards
------------------------------------------+-------------------------------

Comment (by lopo):

 I tried to enable CS checks on the folder, and we get just four sets of
 errors like:

 {{{
  1 | ERROR | [x] When a multi-item array uses associative keys, each value
 should start on a new line.
    |       |
 (WordPress.Arrays.ArrayDeclarationSpacing.AssociativeArrayFound)
  1 | ERROR | [x] File must end with a newline character
 (Generic.Files.EndFileNewline.NotFound)

 }}}
 on `navigation/view.asset.php`, `navigation/view.min.asset.php`,
 `file/view.asset.php` and `file/view.min.asset.php` because they all like
 this:

 {{{
 <?php return array('dependencies' => array(), 'version' =>
 '3776ea67846b3bb10fe8f7cdd486b0ba');
 }}}

 Obviously they're trivial problems but as far as I know those files are
 autogenerated, so with my limited knowledge of Gutenberg I'm not sure what
 can be done about them.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50010#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform