Skip to content

Validation - On-The-Fly loaded defaults might need validation #178

@steiler

Description

@steiler

E.g. the must-stmt validation might load additional data into the tree, by referencing fields that do not yet exist, but carry a default value.
These default values themselfes might carry constratints like leafrefs and must-stmts, which must be validated. (This might even end up in multiple rounds of loading defaults and performing of validation).

I'm somewhat thinking of marking Entries in the Tree as validated and re-running the validation until no new entries are being loaded...
Easiest might be to carry a list forward with all the newly inserted elements. Not sure yet if it makes sense.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions