Closed allynt closed 7 years ago
The logic should be rewritten so that the specific registration fns are called w/in a try/catch
block and execution of the wrapper fn is stopped if an exception is raised.
An explicit test that forces an error is needed.
WHO: @allynt
The registration process is split into 2 fns: a wrapper fn and another registration fn specific to whether or not the ontology is CIM1 or CIM2 - the former calls the latter. If the specific fn fails for some reason, it adds an error message and returns immediately. This is good. However, the wrapper fn still continues by setting "is_registered" to True and doing some other behind-the-scenes stuff. This is bad.