Hi @vasib, thanks for the question, that raises a good point.

All depends at which level you consider the validation. Currently, the BadValueError runtime check is used to check if a model conforms well to its metamodel, at runtime. This means that if you designed a EAttribute (or EReference) to accept only a certain type (e.g: strings), and you try to put a int or another value in it, this exception will be raised. Same thing if you try to insert a value of a wrong type in a collection.

However, there is currently no out-of-the-box support for a custom validation in the sense of "validating my model regarding my domain". So, if you want to validate your model depending on some extra rules, then you need to write the validator yourself (e.g: this property on this instance of EClass should be between this value and this value, ...etc). To help, there is a bunch of functions and concepts in PyEcore that can be useful: single dispatch to go accross a full model.

In the past, I started to write something that was suppose to be generic enough to fit various validation scenarios, but at the end, I wasn't convinced by the API it provided and the way to write rules.

Any validation support? #137

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions