Nicholas Blumhardt comments

Results 944 comments of


                                            Nicholas Blumhardt

Extend support for static accessor to any type (not only interfaces or abstract classes)

I'm working through open issues and closing most of those that have no activity in the past 12 months as `stale`. This helps us track and prioritize the issues that...

Settings: Allow to disambiguate different calls to same method resulting in same key

I'm working through open issues and closing most of those that have no activity in the past 12 months as `stale`. This helps us track and prioritize the issues that...

Optionally write final layer of ToMaximumDepth as ScalarValue instead "Null"

Seems as though this one is stale; still a really interesting idea if anyone decides to look into it, but I'll close this as it's now been quite some time...

Padding not applied in output templates when property values are missing

_Serilog.Expressions_ has some features that should now cover everything discussed in this PR. I'm still interested in improving this behavior, but since it's been stale for so long I'll close...

Documentation : explicitly document the format of accepted values for settings in AppSettings / Configuration

I'm working through open issues and closing most of those that have no activity in the past 12 months as `stale`. This helps us track and prioritize the issues that...

Snapshot exception information before propagating to asynchronous sinks

I'm working through open issues and closing most of those that have no activity in the past 12 months as `stale`. This helps us track and prioritize the issues that...

KeyValuePairSettings / strict mode

I'm working through open issues and closing most of those that have no activity in the past 12 months as `stale`. This helps us track and prioritize the issues that...

F# extension methods aren't picked up by configuration

I have a feeling an unlinked PR addressed this already; please let me know if not and it's still an issue. Thanks!

Add more context information to SelfLog if log statement fails

👍 I think we're now discussing this and related issues over in serilog/serilog.

Logger should have its own scope rather than a global wide scope on provider

Thanks for raising this. Unfortunately it's a behavior that the ship has sailed on, and is unlikely to change at this point. Thanks again for taking the time to explain...