Schema type incorrectly set when omitted and enums given

[spacether]

Schema type incorrectly set when omitted and enums given

Swagger-parser version: 2.0.31

Sample spec:

openapi: 3.0.3
info:
  title: openapi 3.0.3 sample spec
  description: sample spec for testing openapi functionality, built from json schema
    tests for draft6
  version: 0.0.1
paths: {}
components:
  schemas:
    SimpleEnumValidation:
      enum:
      - 1
      - 2
      - 3
    HeterogeneousEnumValidation:
      enum:
      - 6
      - foo
      - []
      - true
      - foo: 12
    HeterogeneousEnumWithNullValidation:
      enum:
      - 6
      - null
    EnumWithEscapedCharacters:
      enum:
      - 'foo

        bar'
      - "foo\rbar"
    EnumWithFalseDoesNotMatch0:
      enum:
      - false
    EnumWithTrueDoesNotMatch1:
      enum:
      - true
    EnumWith0DoesNotMatchFalse:
      enum:
      - 0
    EnumWith1DoesNotMatchTrue:
      enum:
      - 1
    NulCharactersInStrings:
      enum:
      - "hello\0there"

When parsing the above schema, type should be unset on all components
When one checks

• SimpleEnumValidation, the parser incorrectly set type to number when it should remain unset.
• HeterogeneousEnumValidation, the parser incorrectly sets the type to number when it should remain unset
• This issue applies to all other components except for EnumsInProperties which correctly has type set to object

[spacether]

This bug prevents spec writers from making enums with any type (unset type)

[frantuma]

This has been fixed in #1768 with usage of new inferSchemaType option. By setting it to false type will not be anymore inferred