Hi 馃憢 ,
Many thanks for all the work here, I'm very glad to parse some YAML files without thinking to it.
Today I had to investigate about a bit more, since a user made us an unexpected feedback, especially for Norwegian 馃嚦馃嚧 people.
Let's take this yaml file about languages:
language:
type: string
enum:
- en
- fr
- no
- itAfter some parsing for OpenAPI documentation, generated description was:
Values are en, fr, false, it
Obviously, Norwegian language was translated as false.
Digging into this, I understood it was YAML normal behavior for version 1.1, and that it will be changed with YAML 1.2
Of course we've suggested a workaround, to adapt YAML file with 'no' instead of no.
But just for asking, do you plan to support this new YAML spec version?
Hi 馃憢 ,
Many thanks for all the work here, I'm very glad to parse some YAML files without thinking to it.
Today I had to investigate about a bit more, since a user made us an unexpected feedback, especially for Norwegian 馃嚦馃嚧 people.
Let's take this yaml file about languages:
After some parsing for OpenAPI documentation, generated description was:
Obviously, Norwegian language was translated as
false.Digging into this, I understood it was YAML normal behavior for version 1.1, and that it will be changed with YAML 1.2
Of course we've suggested a workaround, to adapt YAML file with
'no'instead ofno.But just for asking, do you plan to support this new YAML spec version?