[wp-trac] Re: [WordPress Trac] #5341: New wp.getCommentModerationCount XML-RPC method

[WordPress Trac]

#5341: New wp.getCommentModerationCount XML-RPC method
-------------------------+--------------------------------------------------
 Reporter:  josephscott  |        Owner:  anonymous
     Type:  enhancement  |       Status:  new      
 Priority:  normal       |    Milestone:  2.4      
Component:  XML-RPC      |      Version:           
 Severity:  normal       |   Resolution:           
 Keywords:  has-patch    |  
-------------------------+--------------------------------------------------
Comment (by redsweater):

 I applaud the enthusiasm to add new support to the API, but I'm worried
 that jumping right on ideas like this might not be the way to go about it.
 Developing and adding to the API should come with some deliberation, and
 should strive to expose as much information from the system as possible,
 in a way that is consistent with the rest of the API.

 I feel like the plugin is cool, and allowed the author to achieve
 something cool. But it's such a pinpointed piece of information, it seems
 really weird to expose just this through the API without thinking about
 all the other related information that might be exposed along with it. Why
 just the moderated comment count? Why not the comment details that go
 along with it? Why not the UNmoderated comments?

 I don't think you should let the very narrow goals of the plugin dictate
 what your API looks like. The development of the API over the years has
 been frustratingly slow at times, but surely this can wait for more than a
 few days after the plugin was released before it creeps into the supported
 API?

-- 
Ticket URL: <http://trac.wordpress.org/ticket/5341#comment:1>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software