Null handling

[erndob]

I'm trying to test the yarm-cli and I'm observing some breaking changes that happen when you convert json->yaml->json.

json, when having schema type set as nullable string:

"type": [
       "string",
       "null"
    ]

yaml:

  type:
  - string
  - null

json:

  "type": [
    "string",
    null
  ]

The null string is parsed back as just a null, instead of a string. This makes it impossible to use. Any workarounds?

I tried having null as 'null' and "null" in yaml, but it always gets converted to a null. Really need to have it as a string.

[justinyoo]

This is more on the YamlDotNet side. I left an issue there to have a look. Kind regards, Justin Yoo | Microsoft MVP | aliencube.org | devkimchi.com

…

On 27 Feb 2019, at 01:04, erndob ***@***.***> wrote: I'm trying to test the yarm-cli and I'm observing some breaking changes that happen when you convert json->yaml->json. json, when having schema type set as nullable string: "userCode": { "type": [ string", "null" ] }, yaml: `entityCode: type: string null json:"userCode": { "type": [ "string", null ] }, ` The null string is parsed back as just a null, instead of a string. This makes it impossible to use. Any workarounds? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.