Skip to content

Validation issue in oneOf when elements have optional fields #185

Closed
@ddobrin

Description

@ddobrin

Currently, oneOf validates each element in the schema.

2 problems need to be addressed:

  • prevent more than one element to be passed in oneOf - violation of OpenAPI spec
  • address the PropertiesValidator, which can not distinguish whether a missing node is an optional field or one of the oneOf elements which is not present in the request

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions