[wp-trac] [WordPress Trac] #41121: Consistency of the _deprecated_function() calls and related documentation.

[WordPress Trac]

#41121: Consistency of the _deprecated_function() calls and related documentation.
----------------------------+---------------------------
 Reporter:  jrf             |       Owner:  DrewAPicture
     Type:  task (blessed)  |      Status:  reviewing
 Priority:  normal          |   Milestone:  4.9
Component:  General         |     Version:  trunk
 Severity:  normal          |  Resolution:
 Keywords:  has-patch       |     Focuses:  docs
----------------------------+---------------------------

Comment (by boonebgorges):

 Replying to [comment:18 DrewAPicture]:
 > @boonebgorges Seeking feedback on hard-deprecation of individual methods
 within `WP_User_Query`, which was itself deprecated in 3.1.
 >
 > Separately, #41125 has been opened, which would allow for drawing a
 distinction between the class itself being deprecated from its methods
 (though, realistically, if the class is deprecated, do we really ''need''
 to also mark the individual methods as deprecated?). Interested in your
 perspective here. See [attachment:0004-missing-_deprecated_function-calls-
 methods.patch].

 "Hard" (maybe better to say "explicit" or "complete"?) deprecation seems
 fine to me, and has the advantage of being consistently explicit. Can you
 say a bit more about why this feels redundant to you? Is it because of the
 additional lines of code
 (the `_deprecated_function()` calls themselves) and the maintenance burden
 they may represent? Or is it because of some redundancy it'd introduce in
 the autogenerated documentation?

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