[Koha-devel] Fundamental flaw in Koha REST API

[Tomas Cohen Arazi]

I recall we used the header at some point, to keep the base query clean
when adding new filters.

The only alternative is forcing the use of some form of ascii encoding
(base64?) But I agree we should better deprecate it.

It's use in the codebase on DT is tied to an option switch and probably not
used



El lun, 5 dic 2022 20:08, Galen Charlton <gmc at equinoxoli.org> escribió:

> Hi,
>
> On Mon, Dec 5, 2022 at 5:40 PM David Cook <dcook at prosentient.com.au>
> wrote:
> > At the moment, it’s not widely used by Koha itself, so I don’t think
> > it will be hard to remove from Koha, but any third-party integrations
> > would need to refactor to use a different option.
>
> This might not be a huge factor, though of course removing that header
> should go through a deprecation procedure.
>
> Specifically, upon skimming the results of a GitHub search of
> "x-koha-query", the only uses I found outside of Koha itself were in
> plugins published by a couple active community members.
>
> Regards,
>
> Galen
> --
> Galen Charlton
> Implementation and IT Manager
> Equinox Open Library Initiative
> gmc at equinoxOLI.org
> https://www.equinoxOLI.org
> phone: 877-OPEN-ILS (673-6457)
> direct: 770-709-5581
> _______________________________________________
> Koha-devel mailing list
> Koha-devel at lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : https://www.koha-community.org/
> git : https://git.koha-community.org/
> bugs : https://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20221205/d6b096b3/attachment-0001.htm>