Feature Request 🛍️
Utilities in this library are raising JS Error, like this. Instead we can at least raise the BaseException class from concerto-core.
Use Case
We make use of the BaseException downstream to distinguish concerto errors. However if the error is raise by metamodel utilities, we would need to check the message. This would help us categorise the error raised.
Possible Solution
Extend the BaseException class from concerto-core to define a new error class or create a new base class for this library.
Context
Detailed Description