using enum in schema leads to unexpected results

Hi

With the following schema:

    EnumBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              enum:
                - foo
              required:
                - foo
              properties:
                foo:
                  type: string

A call with body set to {foo: 'bar', bogus: 'baz'} is rejected (which is expected), but a call with body set to {foo: 'bar'} is also rejected which is not expected.

Is this a bug or did I misunderstood OpenApi specification ?

If needed I can provide a patch so that express-openapi-validator’s tests show this behavior.

All the best

[dod38fr]

Yes ! this resolves my problem.

On the other hand, you might want to check why specifying enum with properties leads to weird results. I would have expected a consistent behavior or an error.

Feel free to leave this bug open to track this issue or to close it.

Thanks for the help ! 😃

All the best

[cdimascio]

Woop! Excellent news! I’m glad it worked out.

The validator is properly handling the enum cases. There are examples of them working in the tests. I’m fairly certain that the specification you provided above is not behaviorally valid, despite it passing validation. Enums describe values and not keys. The OpenAPI spec allows one to define an enum property as a type object, however, the value should also be an object.

I’ll keep this open while I validate this is indeed the case.