Prevent crash in createExample when a multi variant type is being parsed. All variants are concatinated with '|'. Also added a "null" type wich is not the """null""" type, made sure to extra check against this.

[brymko]

While running this project on our API generated OAPI spec i found it to be crashing when running into variant types. For instance incase there is an optional field:

"properties": {
  "is_active": {
    "type": [
      "boolean",
      "null"
    ]
  }

This merge is forwarding my local fix

[netlify]

✅ Deploy Preview for docusaurus-openapi ready!

Name	Link
🔨 Latest commit	b5698a4
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-openapi/deploys/67770dfdeb8afb0008bf8df0
😎 Deploy Preview	https://deploy-preview-267--docusaurus-openapi.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[brymko]

Im not sure if my default assumption of concating everyting with "|" together holds. Because this is only an example maybe we only want the first element ?|

As an example, this would be generated with the proposed changes:

curl -L -X GET 'some_path'' \
-H 'Content-Type: application/json' \
-H 'Accept: text/plain; charset=utf-8' \
-d '{
  "is_active": "true | null",
 }

Now this would obviously be rejected by the server, but so would all context aware data. And given that this should only server as a default i think it might be fine. Open for thoughts.

[bourdakos1]

Is this valid OpenAPI? I would expect the spec to look something like this:

"properties": {
  "is_active": {
    "type": "boolean",
    "nullable": true
  }
}