Add option - [assembly: LogMinimalMethodName]

[GW-Kang]

Is the proposal related to a problem

We can clearly know the class that writes the log through the following syntax generated by Anotar.
static ILogger logger = Log.ForContext();

Also know LineNumber through Anotar's elegant feature.
Therefore, since Class and LineNumber are recorded accurately, there is no confusion about which method logs the log due to method overloading.

Given these circumstances, it can sometimes feel superfluous to log the full specification of a Method.
This becomes even worse when there are many parameters of the method.

Describe the solution

So my proposal is that it would be useful to be able to change the behavior like below via [assembly: LogMinimalMethodName] option.

• today :

In NLog

logger.Debug("Method: 'Void MyMethod(Int32, Int32, String, String, String)'. Line: ~12. TheMessage");

In Serilog

logger
.ForContext("MethodName", "Void MyMethod(Int32, Int32, String, String, String)")
.ForContext("LineNumber", 8)
.Debug("TheMessage");

• with [assembly: LogMinimalMethodName] option :

In NLog

logger.Debug("Method: 'MyMethod'. Line: ~12. TheMessage");

In Serilog

logger
.ForContext("MethodName", "MyMethod")
.ForContext("LineNumber", 8)
.Debug("TheMessage");

[ltrzesniewski]

It would be better to configure that in FodyWeavers.xml instead of an attribute.

[GW-Kang]

Wherever it is configured, I think all would be good.

Just because Anotar already has a configuration method that starts with '[assembly:' as shown below, I thought that a similar implementation would be simpler.

[assembly: LoggerFactoryAttribute(typeof(MyUtilsLibrary.LoggerFactory))]
[assembly: LogMinimalMessage]

[SimonCropp]

LoggerFactoryAttribute is in an attribute so it can be type safe

@ltrzesniewski is correct it should be in FodyWeavers.xml

@GW-Kang Sounds good. happy to accept a PR