[wp-trac] [WordPress Trac] #36492: Add `WP_Post_Status` class

[WordPress Trac]

#36492: Add `WP_Post_Status` class
------------------------------------+------------------------------
 Reporter:  flixos90                |       Owner:  DrewAPicture
     Type:  enhancement             |      Status:  reviewing
 Priority:  normal                  |   Milestone:  Awaiting Review
Component:  Posts, Post Types       |     Version:  3.0
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |     Focuses:
------------------------------------+------------------------------

Comment (by johnjamesjacoby):

 Replying to [comment:13 flixos90]:
 > After discussion in weekly Core meeting, it was decided not to use
 abstract classes at this point.

 That's too bad. It's not unlike the base list-table class, where we have a
 specific problem that requires solving, and foreseeable problems that we
 can also architect for and begin solving at the same time.

 In WordPress core, users, comments, and taxonomy terms will (all,
 eventually) derive a great deal of value from a structure around what a
 status includes and details. Without a base class, so far, each of these
 objects has redefined what a status is in a unique (and mostly terrible)
 way. BuddyPress and bbPress have followed suit, unfortunately.

 In plugins, any other imaginable object will likely need a status. Events,
 Downloads, Shopping cart items, Activity streams, Friendship requests,
 Group memberships, etc...

 The current `WP_Post_Status` class is a great start, and hopefully we'll
 be able to use it as a jumping off point for refactoring statuses for the
 other WordPress objects at a later date.

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