http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8007
--- Comment #45 from Jonathan Druart <[email protected]> --- Thanks all 3 of you for your looks! The idea of Service and DataObject was to separate methods for a discharge object from others routines which are not directly linked to the object ("Manager"). Don't you think if we put all the code in a Koha::Discharge package we will get back to a new Koha namespace with big files where responsibilities are not enough separated? What is the problem with having a simple business object? I don't understand where the complexity is added, to me it is simplified. Should I put all methods/routines from Service::Discharge and DataObject::Discharge to Koha::Discharge? I personally think we should not call Koha::Database in pl files, do we agree with that? If you think it is not the way to do, where can I find a RFC / consensus on how developers should develop using oop into Koha? -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
