[wp-trac] [WordPress Trac] #59633: Ensure theme files caching mechanisms are filterable and caches can be manually cleared

[WordPress Trac]

#59633: Ensure theme files caching mechanisms are filterable and caches can be
manually cleared
--------------------------+--------------------------
 Reporter:  afercia       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  6.5
Component:  Themes        |     Version:  trunk
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:  performance
--------------------------+--------------------------
Changes (by hellofromTonya):

 * milestone:  6.4 => 6.5


Comment:

 I'm moving this ticket to 6.5. Why?

 6.4 RC1 is tomorrow. It's too late in the cycle to consider adding filters
 (which are an enhancement) or improving caching mechanisms for additional
 workflows.

 In reading #59591 and this ticket, it seems the ask is to improve the
 theme caching strategies for additional potential user workflows. @afercia
 lists some of the workflows for consideration. These additional workflows
 appear to be enhancements, rather than bugfixes. And there's not yet
 consensus of these workflows do or do not fall into theme development
 mode.

 What about considering https://github.com/WordPress/wordpress-
 develop/pull/5495 for 6.4?

 * It's a big change, as such is concerning this late in the cycle.
 * It's still being discussed and there's not yet consensus to move forward
 with it.
 * As @flixos90 [https://github.com/WordPress/wordpress-
 develop/pull/5495#pullrequestreview-1680121796 notes in the PR], it's a
 "small improvement" that needs tests and testing:
 >Despite the above, what you're doing here partially addresses the
 concerns on the ticket, so I'm not strongly opposed to merging this as a
 small improvement. But we should have unit tests to make sure it doesn't
 introduce problems, especially this late in the cycle.

 However, if these workflows are indeed a must-have, then likely the
 caching changes would shift to revert consideration, given the latest of
 the 6.4 cycle, to give more time to consider additional workflow needs.
 Thus, if indeed must-have for 6.4, then please move this ticket back into
 6.4 to start revert discussions.

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