Schema validator chokes on numbers in scientific notation

Repro:

$ autorest --input-file=https://tripletex.no/v2/swagger.json

Error:

AutoRest code generation utility [version: 2.0.4280; node: v10.4.0]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest

There is a new version of AutoRest available (2.0.4283).
 > You can install the newer version with with npm install -g autorest@latest

   Loading AutoRest core      '/Users/rigibson/.autorest/@microsoft.azure_autorest-core@2.0.4283/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4283)
ERROR: Schema violation: Expected type number but found type string
    - https://tripletex.no/v2/swagger.json:1:242238 ($.definitions.TravelExpense.properties.attachmentCount.maximum)
FATAL: swagger-document/individual/schema-validator - FAILED
FATAL: Error: [OperationAbortedException] Error occurred. Exiting.
Process() cancelled due to exception : [OperationAbortedException] Error occurred. Exiting.

Culprit appears to be this “maximum” property:

"attachmentCount": {
  "type": "integer",
  "format": "int32",
  "readOnly": true,
  "minimum": 0.0,
  "maximum": 2.147483647E9
},

Related to Azure/autorest.typescript#311

[fearthecowboy]

OH FOR &%@(…

My whole life, I thought exclusiveMinimum was a number … well, that tells you how many people use it, because the powershell generator and the whole V3 modeler aren’t using it right.

At the end of the day, this is so typical of JSON Schema – use two properties, when one would have done.

[josh-oakes]

Ah ok, I got that working. It looks like exclusiveMinimum takes a boolean value along with your minimum, this is what worked for me…

"RunningSpeedMultiplier": {
        "format": "double",
        "minimum": 0.00,
        "exclusiveMinimum": true,
        "type": "number"
}

Thanks for the help!