AssertionError: expected 'number' to be 'string'

[gdams]

Describe the bug
It seems that the openapi parser stumbles over when you specify a type as an integer but specify the default in quotes (required for the swagger-ui).

To Reproduce
Steps to reproduce the behavior:

openapi-to-graphql https://staging-api.adoptopenjdk.net/openapi

(node:28060) UnhandledPromiseRejectionWarning: Could not validate OpenAPI Specification 'v3'. expected 'number' to be 'string'
(node:28060) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:28060) [DEP0018] DeprecationWarning: Unhandled promise rejecti

Expected behavior
We should be able to parse the AdoptOpenJDK openapi specification but instead, it errors out.

Additional context
The error comes from the fact that the default is specified in double quotes. Removing the quotes fixes the parser but breaks the swagger-ui

        required: true
        schema:
          default: "8"
          type: integer

For more context see the following links:
microprofile/microprofile-open-api#420
smallrye/smallrye-open-api#300

[Alan-Cha]

@gdams Sorry for the late reply but thank you for filling this issue!

This seems to be an error related to the Swagger/OAS validator package that we use. As a result, this is largely out our hands for the time being.

We do have an issue filed for possibly replacing the library or exposing it somehow so that users can provide their own validator. #334