Add visualization for combined schemas

[cuducos]

JSON Schema specs define fields such as oneOf, anyOf, allOf and not as combining schemas for validation. In our test case, for example, the field path can be either a string or an array of strings and jsv wasn‘t showing that explicitly:

Path

A reference to the data for this resource, as either a path as a string, or an array of paths as strings. of valid URIs.
The dereferenced value of each referenced data source in path MUST be commensurate with a native, dereferenced representation of the data the resource describes. For example, in a Tabular Data Resource, this means that the dereferenced value of path MUST be an array.

Examples

• {"path":["file.csv","file2.csv"]}
• {"path":["http://example.com/file.csv","http://example.com/file2.csv"]}
• {"path":"http://example.com/file.csv"}

This PR enhances the visualizations showing detailed combined schema information:

Path

A reference to the data for this resource, as either a path as a string, or an array of paths as strings. of valid URIs.

The dereferenced value of each referenced data source in path MUST be commensurate with a native, dereferenced representation of the data the resource describes. For example, in a Tabular Data Resource, this means that the dereferenced value of path MUST be an array.

Validation

It must satisfy one of these conditions

Path

(string)

A fully qualified URL, or a POSIX file path..

Implementations need to negotiate the type of path provided, and dereference the data accordingly.

Examples

• {"path":"file.csv"}

• {"path":"http://example.com/file.csv"}

(array)

Examples

• ["file.csv"]

• ["http://example.com/file.csv"]

Examples

• {"path":["file.csv","file2.csv"]}

• {"path":["http://example.com/file.csv","http://example.com/file2.csv"]}

• {"path":"http://example.com/file.csv"}