[wp-trac] [WordPress Trac] #14994: Introduce a way to identify a hook in progress

[WordPress Trac]

#14994: Introduce a way to identify a hook in progress
---------------------------------------------+------------------
 Reporter:  nacin                            |       Owner:
     Type:  enhancement                      |      Status:  new
 Priority:  normal                           |   Milestone:  3.9
Component:  Plugins                          |     Version:
 Severity:  normal                           |  Resolution:
 Keywords:  has-patch commit has-unit-tests  |     Focuses:
---------------------------------------------+------------------

Comment (by Denis-de-Bernardy):

 Replying to [comment:15 ericmann]:

 In my own code ghetto, a test is meant to allow, when the underlying
 implementation details changes, to validate that -- because the tests
 still pass -- things still work as defined and expected for whoever
 consumes the API. That is useful. And meaningful.

 The suggested tests, in contrast, say nothing about whether the APi works;
 only about whether the APi's internals are left unchange. Whoever changes
 the internals will need to rewrite the tests. This means an extra burden
 on future contributors who decide to do so, with no benefit. It is useless
 and meaningless.

 But anyway... Let's not get that in the way of getting the actual patch
 checked in... +1 for getting the new functionality into WP.

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