Skip to content

Using const values does not set the expected value when validation fails #7

Description

@jpettit

See this example where the validation failed because it was expecting "environment" to be equal to 'foobar'. The report displays the expected value as undefined when it should be foobar.

 Message: Response body is invalid: environment should be equal to constant

  Actual value: local

  Expected value: undefined

  Property: validate.body.properties.environment.const

  JSON schema:
    const: foobar

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions