[Koha-devel] Discussion about internal API design.

[Martin Renvoize]

The Koha namespace is already starting to suffer from many of the issues we
encountered within C4, with rather organic growth.

I've been trying to promote some api design discussions in
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11983.

To summarise, rather than adding lots of ->search_for_x, ->search_for_y,
->search_for_z methods to our objects I'd like to come up with some
guidelines on code re-use and method naming conventions. (along with
improving our current perldoc procedure to make the docs more informative
and helpful, but let's cover that in another bug ;) ).

Please take a look at the example code options I've presented in the bug
and chip in with your thoughts, suggestions. Jonathan has already made some
great suggestions and I'd love to see us working towards having clearer
conventions and more code re-use.

Thanks in advance,

*Martin Renvoize*

Development Manager




*T:* +44 (0) 1483 378728

*F:* +44 (0) 800 756 6384

*E:* martin.renvoize at ptfs-europe.com

www.ptfs-europe.com



<https://www.ptfs-europe.com>



Registered in the United Kingdom No. 06416372   VAT Reg No. 925 7211 30

The information contained in this email message may be privileged,
confidential and protected from disclosure. If you are not the intended
recipient, any dissemination, distribution or copying is strictly
prohibited. If you think that you have received this email message in
error, please email the sender at info at ptfs-europe.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20180719/926b39c9/attachment.html>