[wp-trac] [WordPress Trac] #57832: Multiple classes should be in separate files (class-wp-block-parser.php)

[WordPress Trac]

#57832: Multiple classes should be in separate files (class-wp-block-parser.php)
----------------------------------------------+----------------------------
 Reporter:  aristath                          |       Owner:
                                              |  SergeyBiryukov
     Type:  enhancement                       |      Status:  accepted
 Priority:  normal                            |   Milestone:  6.3
Component:  Editor                            |     Version:  6.2
 Severity:  normal                            |  Resolution:
 Keywords:  has-patch commit gutenberg-merge  |     Focuses:  coding-
                                              |  standards
----------------------------------------------+----------------------------
Changes (by peterwilsoncc):

 * component:  General => Editor


Comment:

 The PR looks ready to commit, having discussed this with @isabel_brison
 I'll be committing this seperately to the other package updates as it's a
 little more complex than the usual package update.

 In order to retain the history in the new files, I'll be running the
 following commands:


 {{{
 svn cp ./src/wp-includes/class-wp-block-parser.php ./src/wp-includes
 /class-wp-block-parser-block.php
 rm ./src/wp-includes/class-wp-block-parser-block.php
 svn cp ./src/wp-includes/class-wp-block-parser.php ./src/wp-includes
 /class-wp-block-parser-frame.php
 rm ./src/wp-includes/class-wp-block-parser-frame.php
 gh pr diff 4152 --repo=WordPress/wordpress-develop | patch -p1
 }}}

 The `rm` commands are to make sure `patch` doesn't get upset creating the
 files but doesn't affect the history.

 I've moved this ticket to the Editor component as the bulk of the changes
 come from the upstream Gutenberg repo.

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