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
I think that for now, we should keep it simple and just implement support for calling methods and extension methods on Serilog.Configuration.LoggerDestructuringConfiguration but not support the generic overloads, and only support parameter types that are currently supported by the configuration systems (i.e. no Func<> or Action<> so far).
This would also encourage developers of DestructuringPolicys to provide extension methods for a more friendly API and consistency with other configuration parts (Sinks, Enrichers etc).
Defining if and how we support calls to generic methods should probably be done in a separate issue.
The text was updated successfully, but these errors were encountered:
tsimbalar
added a commit
to tsimbalar/serilog
that referenced
this issue
Jun 7, 2018
Supports Serilog "native" non-generic simple methods :
- `ToMaximumCollectionCount`
- `ToMaximumDepth`
- `ToMaximumStringLength`
and any *extension method* for `LoggerDestructuringConfiguration`
This should fixserilog#1172
Supports Serilog "native" non-generic simple methods :
- `ToMaximumCollectionCount`
- `ToMaximumDepth`
- `ToMaximumStringLength`
and any *extension method* for `LoggerDestructuringConfiguration`
This should fixserilog#1172
In order to implement serilog/serilog-settings-appsettings#20 it actually needs to be implemented in the core Serilog repo.
Similar feature is already implemented in Serilog.Settings.Configuration via serilog/serilog-settings-configuration#110 and discussed in serilog/serilog-settings-configuration#106 .
I think that for now, we should keep it simple and just implement support for calling methods and extension methods on
Serilog.Configuration.LoggerDestructuringConfiguration
but not support the generic overloads, and only support parameter types that are currently supported by the configuration systems (i.e. noFunc<>
orAction<>
so far).This would also encourage developers of
DestructuringPolicy
s to provide extension methods for a more friendly API and consistency with other configuration parts (Sinks, Enrichers etc).Defining if and how we support calls to generic methods should probably be done in a separate issue.
The text was updated successfully, but these errors were encountered: