Don't know if this has been reported elsewhere already but I couldn't find an equivalent.
Currently some root cause of errors are suppressed and a new error is returned instead.
- For example this code returns "Could not dereference Z7K1", but that is not very helpful. The underlying error "Generic type function did not return a Z4: {"Z1K1":"Z9","Z9K1":"Z8"}" is much more helpful.
Returning the underlying error, possibly while wrapping it in another error, would be much better. Currently the only way to retrieve this information is to add ad-hoc log messages in the orchestrator while debugging.
Update: the specific instance of this problem linked in this code above has been fixed.
- Should also examine all other instances of responseEnvelopeContainsError to see if there are any other errors that get discarded. (Note: containsError got renamed to responseEnvelopeContainsError.)
In the following cases, consider whether the result from ValidationStatus.getZ5() should be encapsulated:
- if ( !validatesAsBoolean( result.Z22K1.asJSON() ).isValid() ) { (builtins.js, line 438)
- if ( !validatesAsBoolean( headEqualityZ22.Z22K1.asJSON() ).isValid() ) (builtins.js, line 524)