https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42592
Bug ID: 42592
Summary: Flag +count embeds that cannot be sorted
Initiative type: ---
Sponsorship ---
status:
Product: Koha
Version: Main
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P5 - low
Component: REST API
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
CC: [email protected]
Depends on: 41950
After bug 41950, +count embeds backed by a DBIC relationship are automatically
sortable. However, some +count embeds are only computed at the Perl level (no
matching DBIC relationship) and cannot be sorted. Currently, consumers discover
this only by receiving a 400 error when attempting to sort.
We need a mechanism to flag or advertise which +count embeds are sortable and
which are not. This could be:
1. An annotation in the OpenAPI spec (e.g. x-sortable: false on the embed enum
value)
2. A response header listing sortable fields
3. Documentation in the API markdown
4. A dedicated endpoint or metadata response
The goal is to let API consumers know upfront which +count columns support
sorting, without trial and error.
Discussion started in bug 41950 comment 17.
Referenced Bugs:
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41950
[Bug 41950] Make +count embeds sortable by using SQL-level COUNT subqueries
--
You are receiving this mail because:
You are watching all bug changes.
You are the assignee for the bug.
_______________________________________________
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/
