Extend validation to validate multiple resources with the same schema

[mcweba]

Current validation feature

Let's say you have the following structure of resources and want to validate the res_1, res_2 and res_3 resource.

To validate these resources, you would have to deploy 3 different schemas and configure them in the validation resource like this:

{
  "resources": [
    {
      "url": "/playground/server/tests/resources/res_1",
      "method": "PUT"
    },
    {
      "url": "/playground/server/tests/resources/res_2",
      "method": "PUT"
    },
    {
      "url": "/playground/server/tests/resources/res_3",
      "method": "PUT"
    }    
  ]
}

Required additional validation functionality

So when res_1, res_2 and res_3 are instances of the same resource and therefore can be validated by the same schema, it would be useful to define one schema only.

It would be useful when the configuration could look something like this:

{
  "resources": [
    {
      "url": "/playground/server/tests/resources/.*",
      "method": "PUT"
    }    
  ]
}

This would mean that all resources under /playground/server/tests/resources/ will be validated. It has to be defined how the corresponding schema for this resources can be selected (maybe by defining the name of the schema as additional property in the validation resource).

[lbovet]

Is it not already the case when using the _ placeholder in the schema path?

[mcweba]

You're absolutely right, using the underscore (_) in the schema path does the trick. Maybe the documentation is a little bit weak here 😉