Skip to content

Property Validation: exclusiveMaximum #19

Open
@everettraven

Description

@everettraven

The exclusiveMaximum constraint on a property enforces that the value is up to but not including the maximum constraint.

Changing from an inclusive maximum to an exclusive maximum would be a breaking change as it shrinks the range of allowed values and thus breaks client/user expectations and may invalidate existing instances that use the inclusive maximum value.

Going from an exclusive maximum to an inclusive maximum would generally be OK as you would be expanding the range of allowed values and not be invalidating existing instances or client/user expectations of existing values that would work.

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