https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26555
--- Comment #18 from Tomás Cohen Arazi <[email protected]> --- (In reply to Jonathan Druart from comment #16) > Tomas, I am not a fan of this, and I am wondering if the following approach > would not be better. > > Imagine you have one or more messages (ie. not blocking errors) to pass to > the caller, then you could throw a Koha::Exception::Messages (or > Koha::Exception::Errors?) that would contain a set of Koha::Exception. > That would allow us to tell the callers several things happened, and let it > handle the situation how it wants. > > What do you think? If you think we have time to have it in master for the next release, I can work on removing this generic thing from Koha::Object and only keep the message encapsulating class (Koha::Object::Message), and introduce a Koha::Exception::Object::Messages exception that carries a list of Koha::Object::Message objects. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://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/
