I have a repo layout with a directory of json files, and a custom JSON Schema in a subdir which I would like to use to validate them:
I cannot find a way to configure the JSON Schema Mappings to validate file1.json & file2.json, without it also attempting to validate myConfigSchema.json as it's own custom format (not as JSON schema format)
Using either of:
- a "File path pattern" of `config\*.json`
- a "Directory" of `config`
both result in unwanted validation of `myConfigSchema.json` as it's own format, and it being annotated with many errors.
If an extra mapping is added of `config\schema\myConfigSchema.json` as "JSON schema v6"; an error is given "There are several JSON schemas mapped to this file"
Is this a bug/limitation, or is there some way to workaround?