Rolf Kristensen
Rolf Kristensen
Right now NLog v5 supports use of [caller-member-attributes](https://nlog-project.org/documentation/v4.7.0/html/M_NLog_LogEventInfo_SetCallerInfo.htm) to avoid capture of full stacktrace. It could nice if the CallSite with `captureStackTrace=false` still was able to extract the callsite from...
Make `LogFactory.Flush()` synchrone without spinning up threads. Instead provide `Task FlushAsync()` if wanting parallel target-flush capability. Allow NLog to work out-of-the-box on platforms with limited thread-support. See also #4266
- [ ] Waiting for NLog v5.3 Skip allocation of the `LogEventInfo.Properties`-dictionary, when `TraceEventType.Verbose`. Align Filter-behavior for all Write-methods to match default TraceListener-implementation: - Write(string message) - Write(object o) -...
Maybe stop using typed `Layout` inside `ValueTypeLayoutInfo`. See also #5258 + #3366
- [ ] Waiting for NLog v5.3 (Since breaking behavior change) To improve this use-case with NET6/NET7/NET8 (not specifying any namespace): ``` using NLog; var logger = LogManager.GetCurrentClassLogger(); ``` Fallback...
- [ ] Waiting for NLog v5.3 Just like LogFactory should be platform-independent (Not require console or filesystem), then the same goes for InternalLogger.
RegularExpression is a heavy dependency for a logging library, when using AOT. Instead create dedicated RegEx-Replace-LayoutRenderer, and change the `MultiplePatternLoggerNameMatcher` to not rely on RegEx.
- [ ] Waiting for NLog v5.3 I don't like the word "unsafe", and since the attribute is just a restriction of the original `ThreadAgnosticAttribute`, then I think `[ThreadAgnosticImmutable]` is...
- [ ] Waiting for NLog v5.3
- [ ] Waiting for NLog v5.3 Fix bad naming introduced with #5248 (`_wrapped` was a bad choice)