add parameters from schema top level as expected params

[mirpedrol]

Parameters defined in the schema top level or within definitions are considered expectedParams.

{
  "$schema": "http://json-schema.org/draft-07/schema",
  "type": "object",
  // Top level params
  "properties": {
    "test_param_1": { 
          "type": "string"
        }
  },
  // Definition groups
  "definitions": { 
    "my_group_of_params": { 
      "title": "A virtual grouping used for docs and pretty-printing",
      "type": "object",
      "required": ["foo", "bar"], 
      "properties": { 
        "foo": { 
          "type": "string"
        },
        "bar": {
          "type": "string"
        }
      }
    },
    // Params within definitions but not inside one of the definitions
    "properties": {
      "test_param_2": { 
        "type": "string"
      }
    }
  },
  // Contents of each definition group brought into main schema for validation
  "allOf": [
    { "$ref": "#/definitions/my_group_of_params" } ,
    { "$ref": "#/definitions" } 
  ]
}

[ewels]

// Params within definitions but not inside one of the definitions

This one is non-valid JSON schema. It would be parsed as a definition group called properties, then containing unrecognised keys.

I don't think that we need to consider this scenario? Just within definitions (as already done) and in the top level.

[ewels]

Great! I think that part of the support you've added is probably overkill and not needed, but still fine either way 👍🏻 😃

[ewels]

I don't think that we need this one..