[wp-trac] [WordPress Trac] #60078: Fix the Generic.Formatting.MultipleStatementAlignment.IncorrectWarning linter warning in WP_HTML_Tag_Processor

[WordPress Trac]

#60078: Fix the Generic.Formatting.MultipleStatementAlignment.IncorrectWarning
linter warning in WP_HTML_Tag_Processor
------------------------------+-------------------------------
 Reporter:  antonvlasenko     |       Owner:  SergeyBiryukov
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:  6.5
Component:  HTML API          |     Version:  trunk
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch commit  |     Focuses:  coding-standards
------------------------------+-------------------------------

Comment (by hvlvaetd77):

 To fix the
 `Generic.Formatting.MultipleStatementAlignment.IncorrectWarning` linter
 warning in the `WP_HTML_Tag_Processor` class, you'll need to backport the
 changes from the related pull request in Gutenberg to the WordPress Core
 codebase. Here's a guide on how to do that:

 1. **Identify the Pull Request**: Locate the pull request with the
 identifier https://github.com/WordPress/gutenberg/pull/57030. This pull
 request contains the necessary code style fix for the
 `WP_HTML_Tag_Processor` class.

 2. **Review the Changes**: Before backporting the changes, review the code
 modifications introduced in the pull request to ensure they address the
 linter warning without introducing any new issues.

 3. **Apply the Changes to WordPress Core**: Manually apply the changes
 from the pull request to the corresponding file in the WordPress Core
 codebase. In this case, you'll need to update the `WP_HTML_Tag_Processor`
 class file with the changes made in the pull request.

 4. **Test the Changes**: After applying the changes, thoroughly test the
 affected functionality to ensure that the fix works as expected and does
 not cause any regressions or new issues.

 5. **Commit the Changes**: Once you're satisfied with the changes and they
 have been tested successfully, commit the modifications to the WordPress
 Core codebase.

 6. **Create a Pull Request (Optional)**: If you have permission to
 contribute directly to the WordPress Core repository, you can push your
 changes to a branch and create a pull request for review. Otherwise, you
 may need to submit the changes through the appropriate channels according
 to the WordPress Core contribution guidelines.

 7. **Update Documentation (If Necessary)**: If the changes introduce
 significant modifications or new functionality, make sure to update the
 relevant documentation to reflect the updates.

 8. **Notify Relevant Parties**: Inform other contributors or maintainers
 about the backport and any associated changes to ensure visibility and
 coordination.

 By following these steps, you can effectively address the
 `Generic.Formatting.MultipleStatementAlignment.IncorrectWarning` linter
 warning in the `WP_HTML_Tag_Processor` class and align the codebases of
 Gutenberg and WordPress Core.

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