[PEPr] +1 for Web Services::Services_UseKetchup

From: Date: Wed, 08 Sep 2010 23:36:10 +0000
Subject: [PEPr] +1 for Web Services::Services_UseKetchup
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-53777@lists.php.net to get a copy of this message
Daniel O'Connor (http://pear.php.net/user/doconnor) has voted +1 on the proposal for Web Services::Services_UseKetchup. Proposal information: http://pear.php.net/pepr/pepr-proposal-show.php?id=628 Vote information: http://pear.php.net/pepr/pepr-vote-show.php?id=628&handle=doconnor This vote is conditional. The condition is: Bunch of trivial nitpicks; sorry for not commenting earlier! I know you've done it to save you writing code, but work in the constructor scares me a touch :S - $this->getApiToken(); Ditto instantiating classes in places that aren't the constructor - makeRequest() for instance. Also having some of the unit tests incomplete because a certain user account doesn't work :( PHPUnit's getMock() or HTTP_Request2's Mock Adapter ftw. From an overall API perspective; it might be worth splitting up the "create me a bunch of classes, wire them together with these credentials" behaviour into a different class (Services_UseKetchup_Factory) from the "execute these API calls and give me data" code in the core class. I can see you've sort of done it with Services_UseKetchup_Common; but I'd encourage you to really define the purpose of each class, and polish its responsibilities. Look forward to seeing it in PEAR.

« previous php.pear.dev (#53777) next »