> While that is a simple change it is a breaking change behaviourally. You go
> from a situation where a user gets an explicit error message that they can do
> something about to a situation where some aspects of invalid configurations
> are silently ignored. For complex configurations this may lead to all sorts
> of subtle and invisible errors which uses could waste far more time trying to
> track down than if they had just received an error as they do currently.
Or it could show a log message?
if (m != null)
print (m + " not a valid model. Skipping graph " + gName);
Then it's the responsibility of HDT (or any other custom assembler) to decide
what to do:
- print "file not found" and throw an exception, or
- return null (that in turn will trigger the "invalid model" message), or
- return a DefaultModel
