v3.11.0
What's Changed
Adds an extra validation step in the ModelManager to validate ModelFile object against the Metamodel definition. This is useful for catching errors when dynamically creating model files and to ensure internal consistency.
When opting into this feature:
- In strict mode, invalid models will now throw an error.
- In the default non-strict mode, a console warning is printed.
Turn on the feature with a parameter to the ModelManager constructor, e.g.
new ModelManager({ metamodelValidation: true });
Changelog
- chore(actions): publish v3.10.0 to npm by @github-actions in #686
- feat(core): add validation of model files against metamodel by @mttrbrts in #684
Full Changelog: v3.10.0...v3.11.0