Skip to content

Incorrect fieldsMatch in profile #965

@dtemkin-volpe

Description

@dtemkin-volpe

In the Table Schema documentation, fieldsMatch is described as "MUST be a string with the following possible values and the exact value by default".

However, in the JSON schema for the Table Schema, fieldsMatch is typed as an array as follows:

"fieldsMatch": {
            "type": "array",
            "item": {
                "type": "string",
                "enum": [
                    "exact",
                    "equal",
                    "subset",
                    "superset",
                    "partial"
                ],
                "default": "exact"
            }
        }

It seems to me like the standard describes fieldMatch as a string, but the JSON schema describes it as an array with a singular string item? I'm not really sure which one to follow (or if this is actually an issue, maybe I'm just reading everything wrong), so let me know. Thanks!

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions