https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26790 --- Comment #3 from Julian Maurice <julian.maurice@biblibre.com> --- (In reply to David Cook from comment #2)
(In reply to Julian Maurice from comment #1)
+1 for moving Koha config out of zebra config file +1 for not using XML
But -1 for using YAML. I know we already use YAML for everything in Koha, but YAML has a lot of disadvantages
I'm not finding those links particularly persuasive.
Using Perl's YAML module, I wasn't able to reproduce a single issue from those links. Plus many of the proposed issues should be easily avoidable anyway.
One concrete problem we had in Koha recently was that some MARC field tags starting with 0 were parsed as octal numbers. (040 becomes 32 but 099 remains 99)
Can you point me to a bug report for that one? That sounds very interesting. I couldn't reproduce that problem based on the description.
Can't remember the exact details and can't reproduce either... it was about the ES mappings file, MARC fields being changed when exporting/re-importing... But the real problem IMO is that YAML is implementation dependent. For instance, this document: foo: 040 can be interpreted as { "foo": "040" } or { "foo": 32 } depending on how you read it. (Try this https://onlineyamltools.com/convert-yaml-to-json) Even in Perl where implicit typing seems to be disabled by default, it can be turned on anywhere in the code ($YAML::Syck::ImplicitTyping = 1), so you can never be sure of what will happen. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.