Recent version broke enums with oneOf which is part of the standard

[jhancock-taxa]

Describe the bug
Previous versions didn't validate that enums didn't have oneOf, which was fine. But now it's broken, despite this being part of the V3.0+ standard

OpenApi File To Reproduce
This is valid OpenAPI 3.1:

"DocumentPurposes": {
        "type": "integer",
        "description": "Known purposes for a document",
        "x-enumNames": [
          "IRSFormSchema",
          "IRSFormBusinessRules",
          "IRSFormStyleSheets",
          "IRSFormPDF",
          "IRSFormInstructions",
          "Other"
        ],
        "enum": [
          1,
          2,
          3,
          4,
          5,
          999
        ],
        "oneOf": [
          {
            "const": 1,
            "title": "IRSFormSchema"
          },
          {
            "const": 2,
            "title": "IRSFormBusinessRules"
          },
          {
            "const": 3,
            "title": "IRSFormStyleSheets"
          },
          {
            "const": 4,
            "title": "IRSFormPDF"
          },
          {
            "const": 5,
            "title": "IRSFormInstructions"
          },
          {
            "const": 999,
            "title": "Other"
          }
        ]
      },

Expected behavior
It should validate this and validate as correct because it is THE standard way of defining enums with key/value pairs.

[jhancock-taxa]

Note: Using "enum": [ array here that is the value in the enums list] works as far as it goes reading the file and getting around the validation. However that promptly breaks kiota.

[MaggieKimani1]

@jhancock-taxa thank you for bringing this up. I'll investigate this and get back to you on it.