Skip to content

Property Validation: oneOf #25

Open
@everettraven

Description

@everettraven

The oneOf constraint on a property means that its value is restricted to matching exactly one of the subschemas.

This should probably follow the same pattern as the existing enum property validation where:

  • Adding a new schema to oneOf to an existing oneOf constraint is only OK if it does not result in existing valid values match an existing subschema and the new schema. Default to breaking.
  • Adding a net-new oneOf constraint is breaking
  • Removing a oneOf schema is breaking

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/featureCategorizes issue or PR as related to a new feature.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions