[wp-trac] [WordPress Trac] #35393: should "publish_future_post" be "wp_publish_future_post"?

[WordPress Trac]

#35393: should "publish_future_post" be "wp_publish_future_post"?
-------------------------+----------------------
 Reporter:  ixmati       |       Owner:
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:
Component:  Cron API     |     Version:  4.4.1
 Severity:  normal       |  Resolution:  wontfix
 Keywords:               |     Focuses:
-------------------------+----------------------
Changes (by ericlewis):

 * status:  new => closed
 * resolution:   => wontfix
 * component:  General => Cron API
 * milestone:  Awaiting Review =>


Comment:

 Hi @ixmati, thanks for opening this ticket and welcome to WordPress Trac!

 > I notice that other WP cron jobs called are prefixed by "wp_", but not
 "publish_future_post", which makes it harder to see that this job is part
 of WP core.

 Although it does not have the `wp_*` prefix, it is in the WordPress core
 software, so hopefully this explains that it is part of core.

 The WordPress project has a commitment to backwards compatibility.
 Renaming the event could be a breaking change — a plugin could expect the
 event to be named `publish_future_post`, and changing it would break the
 plugin. @nacin has a good note on
 [https://make.wordpress.org/core/2011/03/23/code-refactoring/ not
 refactoring code] if we don't have to, which is a good read.

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