________________________________________ Fra: koha-devel-bounces@lists.koha-community.org <koha-devel-bounces@lists.koha-community.org> på vegne av koha-devel-request@lists.koha-community.org <koha-devel-request@lists.koha-community.org> Sendt: 16. august 2016 12:00 Til: koha-devel@lists.koha-community.org Emne: Koha-devel Digest, Vol 129, Issue 18 Send Koha-devel mailing list submissions to koha-devel@lists.koha-community.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel or, via email, send a message with subject or body 'help' to koha-devel-request@lists.koha-community.org You can reach the person managing the list at koha-devel-owner@lists.koha-community.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha-devel digest..." Today's Topics: 1. Re: What's on in Koha devel #3 (RESTful API) (Tomas Cohen Arazi) 2. Re: What's on in Koha devel #3 (RESTful API) (Katrin Fischer) ---------------------------------------------------------------------- Message: 1 Date: Mon, 15 Aug 2016 12:54:06 +0000 From: Tomas Cohen Arazi <tomascohen@gmail.com> To: Marcel de Rooy <M.de.Rooy@rijksmuseum.nl>, "koha-devel@lists.koha-community.org" <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] What's on in Koha devel #3 (RESTful API) Message-ID: <CABZfb=WXTfeiMjO7zjccDTjSK7N=-E-MnQC3SPKNvR0VtZUttw@mail.gmail.com> Content-Type: text/plain; charset="utf-8" El lun., 15 ago. 2016 a las 4:28, Marcel de Rooy (<M.de.Rooy@rijksmuseum.nl>) escribi?:

...

= RESTful API = I also would like to know who is willing to maintain this code? For instance on bug 16330 (REST API: add routes to add, update and delete patrons) the delete route is calling # check if loans, reservations, debarrment, etc. before deletion! my $res = $patron->delete So no check is done from the API. But if bug 16907 (Move DelMember and HandleDelBorrower to Koha::Patron) is pushed, $patron->delete will take care of the holds, etc. My question is simple: are we expecting from devs, signoffers and > QAers to update and maintain these routes? Or a dedicated person will update them before each release?

Should our scripts go via REST some day and should all business logic remain in Objects? Etc. etc.

Exactly! What Jonathan noticed, is that no one realized there was a bug on the REST api, this should be reported, and fixed. The more we use the API the more bugs we will find, and the more we will enhance it. I think Marseille will be a good place to work on this. Regards -- Tom?s Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ? +54 9351 3513384 GPG: B2F3C15F