[Koha-bugs] [Bug 26790] Refactor Koha configuration (koha-conf.xml)

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26790

--- Comment #4 from David Cook <dcook at prosentient.com.au> ---
(In reply to Julian Maurice from comment #3)
> 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...

Hmm maybe someone else will surface it later.

> But the real problem IMO is that YAML is implementation dependent.

That's a good point.

> 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)

Thanks for that link. That is interesting.

However, it seems lazy to write it as 'foo: 040'. Surely it would be safer to
explicitly write it as "foo": "040", since we know that they are strings. (That
being said, since Perl is weakly typed, I wonder if Perl would try to convert
that internally into a number...)

> 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.

In theory, we should know, but I reckon that Koha is big enough that it can be
easy to lose track of how the YAML has been set up across the board.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.