Opened 3 years ago
Last modified 3 years ago
#56602 new enhancement
Add a comment to auto-generated editor files pulled from Gutenberg repository
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Awaiting Review | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Build/Test Tools | Keywords: | |
| Focuses: | docs | Cc: |
Description
With the increasing amount of files merged from Gutenberg, it's not always clear which files are safe to patch in core and which should first be patched upstream in the Gutenberg repository and then backported to core.
At a glance, these fall under the latter category:
wp-includes/blocks/* wp-includes/class-wp-block-parser.php
Patching them directly in core would cause a test failure, see comment:10:ticket:56581 for a recent example.
To avoid further confusion, it would be great to add a comment like this at the top of the file:
/*! This file is auto-generated */
similar to the one added in [41271] and [46589] for RTL CSS and minified JS and CSS files.
Or this one from tools/release/sync-stable-blocks.js, added in [53688]:
// This file was autogenerated by tools/release/sync-stable-blocks.js, do not change manually!
If that would require changes in both core and Gutenberg build process, this ticket can be used for tracking. If it can be done entirely on the Gutenberg side, happy to move the issue there.
Related: #55973