You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a core library included in other components, this bypasses whatever other logging mechanisms may be in place (such as slf4j, log4j, etc) and prints directly to the std error output stream. This means some diagnostic logging may be lost, and it also pollutes the output stream in cases where that's not desirable. For example, with the use of CLI tools.
We should remove all instances of Exception::printStackTrace() and either rethrow exceptions, log via a logging API, or ignore as appropriately.
The one exception to that rule is in the case where we're intentionally building a CLI.
The text was updated successfully, but these errors were encountered:
At various places in the CQL libraries Exceptions are caught and stack traces are printed such as here:
https://github.com/cqframework/clinical_quality_language/blob/master/Src/java/quick/src/main/java/org/cqframework/cql/cql2elm/quick/FhirModelInfoProvider.java#L69
For a core library included in other components, this bypasses whatever other logging mechanisms may be in place (such as slf4j, log4j, etc) and prints directly to the std error output stream. This means some diagnostic logging may be lost, and it also pollutes the output stream in cases where that's not desirable. For example, with the use of CLI tools.
We should remove all instances of
Exception::printStackTrace()
and either rethrow exceptions, log via a logging API, or ignore as appropriately.The one exception to that rule is in the case where we're intentionally building a CLI.
The text was updated successfully, but these errors were encountered: