Auto-deduce context when no context is given

[bbottema]

We would like to take the context from the currently dependent service and its parent module.

I think that it will be hard to solve... I post it at stackoverflow.
get-module-and-controllerservicedirective-names-at-runtime

[francescobragagna]

I did'n get the solution: maybe I make a mistake, but if I not get a specific logger instance $log.getInstance('shiningInstance') , when I use simply $log.info('wellcome') inside MyController the result looks like:
10-8-2015 10:02:13::[global]> wellcome
Instead I was hoping to have something like
10-8-2015 10:02:13::[MyController]> wellcome

It's something to improve, or should I do something different?
In the linked stackOverflow response is written how define a controller, and inside it the $log is instanciated with controller name... but in this way should I do it for every controller?

[bbottema]

$log.getInstance('shiningInstance') yields a logger instance you should use to do logging.

var logger = $log.getInstance('shiningInstance');
logger.info('welcome');

If you write $log.info('welcome') you are using angular-logger as a drop-in replacement for the old $log.log functions which use 'global' as context name.

[francescobragagna]

I would like to above, in any of my controller, writhe something like:
var logger= $log.getInstance('...');
and than refactor everywhere using logger. instead of $log.
logger.log('abc')

I was thinking there is a way to use $log.info('abc') and the logger take itself the controller name, to produce the logger-enhanced line as configured (controllerName, timestamp...)

[bbottema]

This issue is exactly about what you are looking for. Unfortunately, we have been unable to solve that puzzle yet.

[francescobragagna]

ah, ok, i was thinking the issue was closed because solved! 👍
Thanks for the info. Hope to finding a solution, if I found anything I will add here some comment! cheers