Open
Description
As a user I want to know which schema and property caused an exception so that I can easily identify and fix the problem.
Currently exceptions are raised locally and include information about what is wrong. They do not always include which part of the schema caused the problem. That can make it difficult to spot where in the schema the problem is. Maybe the base exception can include fields around the schema name and property name that can be set in an exception handler around or within the model factory and the message string can overridden to include the properties, if they are set.