This is the first in a series of tickets that will require a refactoring of the client to consider all records of a schema, and all schemas of a dictionary, togehter in the validation step.
The unique restriction expects that each record in the schema has a unique value for the affected field. If the field is not required and the record has an undefined value for this field, then the unique restriction is not considerd.
This restriction can only be applied to the set of records given to the validator. It is therefore the responsibility of the client calling the schema validation client to provide to complete set of records that the uniqueness constraint applies to.
This is the first in a series of tickets that will require a refactoring of the client to consider all records of a schema, and all schemas of a dictionary, togehter in the validation step.
This enforces the restriction detailed in the
lecterncodebase in this issue: https://github.com/overture-stack/lectern/issues/175The
uniquerestriction expects that each record in the schema has a unique value for the affected field. If the field is not required and the record has anundefinedvalue for this field, then the unique restriction is not considerd.This restriction can only be applied to the set of records given to the validator. It is therefore the responsibility of the client calling the schema validation client to provide to complete set of records that the uniqueness constraint applies to.