|
When calling any of the logging functions they output information about the scope the call to log came from. When compiling a catalog the scope information is the name of the resource (class, define), but when running tasks there is no such resource - scope will instead use the path to the file where the logging call takes place.
Those paths can be quite long and clutters the output (makes it hard to read). The logic already shortens paths that are "in the environment", but should also do that for paths into a module.
See TODO comment in Scope.to_s
|