https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41950
Tomás Cohen Arazi (tcohen) <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |Signed Off --- Comment #18 from Tomás Cohen Arazi (tcohen) <[email protected]> --- (In reply to Jonathan Druart from comment #17) > I think we must make it sortable when +count can be embedded, otherwise how > the consumer can know when it's sortable or not? I'm going to provide a follow-up for the trivial cases we didn't do the right thing with relationships (including Koha::Patron->checkouts which is 8yro and we didn't have this infrastructure yet). I don't think this should be a blocker for this enhancement. The current situation is consumers don't know which fields they can sort on, and get a meaningful 400 error when they can't. That's the contract with the API. This dev is making many of those succeed instead of returning the already established 400. We can think of some annotation, some work on the API markdown to alert about this. I'm open to ideas, but pushing this as-is puts us in a better place, overall. Marking SO as it was, while we discuss how to make it even better. -- 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/
