I don't like columns_settings.yml either heh, although that's also a bit of a different case, since it's just a YAML serialization of 1 large data structure, which would be easy to validate.
In this case, we'd be having 1 huge template file with much more complex syntax. But... may as well go ahead and do it. I can't think of any reasons not to that would be real blockers. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- From: Koha-devel <koha-devel-boun...@lists.koha-community.org> On Behalf Of Owen Leonard Sent: Friday, 7 August 2020 9:56 AM To: Koha Devel <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] An idea for consolidating staff interface header search forms On Wed, Jul 15, 2020 at 10:41 PM <dc...@prosentient.com.au> wrote: > > Yeah, I'm not a fan of a single big file either. ... > It looks like that 1 file is 764 lines long For comparison, columns_settings.yml is currently 1434 lines long. -- Owen -- Web Developer Athens County Public Libraries (740) 737-6006 https://www.myacpl.org _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
signature.asc
Description: PGP signature
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
