Default boolean values for yaml are turned into empty strings about mojolicious-plugin-openapi

[jhthorsen]

I'm not sure if I can fix this, since there's no good definition of "false" in YAML. I think you need to take this with the author of YAML.

Please re-open if you have an idea for how to fix this or how to make a workaround.

[ugexe]

i would think one of two things would work:

1. Translate the Yaml to Json, followed by populating the default value (so the default is applied to the json and not the yaml

2. Use introspection after the initial translation - if the type is "boolean" and has an invalid Boolean default it could refer to the original yaml doc and try to extract a truthy or falsey value to be re-applied

[ugexe]

The swagger tools all seem to cope with this, so I would think they are doing something similar

[ugexe]

I can't reopen this issue. Also even if you can't fix it I'm not sure you should close the issue as it only hides the problem from others who may encounter it.

[jhthorsen]

I won't leave issues open that I can't fix.

The problem is that the YAML library converts the word "true" and "false" into something that isn't really a boolean value. What I would like is if the author of the YAML library would convert booleans into JSON::PP::false and ::true objects.

[jhthorsen]

It's really just guesswork. At some point I considered dropping YAML support completely, but I kept supporting it, even if I don't like/use YAML myself.

[jhthorsen]

Actually... You're right: In this case it's not guesswork. Sorry, I think vacation has made me confused :/