I was a late adopter to the REST API . And I’m just talking about
optimizations.
Yeah, the plugins are the most variable part with the spec, and certainly
introduce some risk. Originally when I was looking at the schema validation, I
thought about caching a MD5 checksum of the spec and
I don’t use pbuilder to build Debian packages but Mason does. Have you talked
to him about it?
Are you sure that it’s a yarn/nodejs bug and not a pbuilder configuration issue?
It seems like not having network access when building with pbuilder is the norm:
The original implementation installed yarn inside the pdebuilder image [1].
But THERE'S a yarn/nodejs BUG [2] that prevents it from detecting
networking is available and thus cannot be run.
Looking forward for enhancing pull requests :-D
[1]
This looks like a weird hack to me. When the package is built,
build-resources.PL should be invoked via the Makefile.
What’s the problem that’s leading to this workaround?
David Cook
Senior Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia
A new cycle is about to start. It is time for you all to put your names for
the next release.
Here: https://wiki.koha-community.org/wiki/Roles_for_23.11
Best regards
--
Tomás Cohen Arazi
Theke Solutions (http://theke.io)
✆ +54 9351 3513384
GPG: B2F3C15F
There's a conversation going on on the bug, about how that change made the
build process a bit more complicated (i.e. more steps).
Kyle and I have been working on this:
https://gitlab.com/koha-community/koha-dpkg-docker#usage
which is a simple way to build packages, and considers that required
Koha has been using the Swagger/OpenAPI plugin since... 2015.
The validation step is important, especially when there are API plugins.
Plugins can break the API, and we need to check that. I'd like to hear
opinions about that, though. And I am open to changing my mind.
Best regards
El mié, 26
Hey all,
Years ago, I chatted with the author of Mojolicious::Plugin::OpenAPI about
skipping the schema validation as it was causing extremely high server load.
He added a config option for it in a newer version, and that version is
available for Koha 22.11. I've tried turning on that
