Array Validates Against Schema When It Shouldn't

[loganfrederick]

I've run into an issue where comparing a an array of data successfully validates against a schema I maintain when it shouldn't.

For example, if I have a schema file I maintain called schema.json which has a body like:

{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "title": "My Title",
  "properties": {
    "my_field": {
      "type": "string"
    }
  }
}

Which I know works from validating other non-array JSON objects against it.

But when I set the following variable:

data = [1,2,3]

And call:

errors = JSON::Validator.fully_validate(schema.json, data)

It does not return any errors even though clearly the data array should not match the schema.

One hack workaround I tried is just throwing an error if data, converted to a string, starts with a "[", but that's obviously a hack.

Am I required to use ":strict => true" in this case (I'd rather not so as to allow flexibility in having other fields sent to the Schema Validator)? Has anyone else run into this?

[RST-J]

Why shouldn't it match the schema? The schema does not require 'object' or any particular type for the data. And it only states that if there is a property 'my_field' then it must be of type string, but it may also be absent as it is not declared as required.
I'd agree with you if the validation still succeeds if there is a top-lebel 'type' definition of something that prohibits an array.

[loganfrederick]

@RST-J I was not aware the top-level also had a type "object" available as an option. That fixes it. Thank you for the help!