Open rofr opened 12 years ago
This would be a breaking change, but I'm still curious why a type isn't enough. The source just indicates what instance type owns the logger and nothing more. Can you give me an example of when a name would be better, since I guess you'll only have one logger per instance?
I'm thinking a logger shared by a group of collaborating objects to simplify configuration like filtering. Also, it would be compatible with NLog
A string would allow more flexibility than Type. Should be accompanied by an additional LogKernel.GetLogger(string name) method and a rename of ILogger.Source to ILogger.Name