Nicholas Blumhardt

Ah, yes of course - I forgot that this is implemented using `LevelOverrideMap`. Hmmm 🤔 - changing it there would have a bit more impact and would need more careful...

Thanks for the follow-up. I think log4net was probably the origin of this decision (it was the main influence on conventions in Serilog at the beginning). This needs some thought...

Hi Zach! Thanks for the report and analysis. If you're able to figure out a solution that doesn't regress other existing usages of the library, it would be welcome 👍

Hi Zach - any updates on how the fix went in dd-trace? (No other regressions noticed since then?) :-)

I think this is worthwhile for a 3.0; I don't think we'd get a lot of benefit making the change right now. I checked out your PR along these lines,...

Having spent a bit of time back in the codebase again ---- I think this is worth cutting a 3.0 for; let's make 2.12 the last of the 2.x series,...

I'm in two minds about this one - the syntactic brevity is nice, but since it's not universal (e.g. I'd still need to write `new LogEventProperty(..., new ScalarValue(myScalarType))` for types...

I'm not sure whether we do, it's been a long time since I checked in on the relevance of CLS compliance in the modern .NET world - needs a quick...

Hi, no, this isn't possible today and would be very unlikely to make it into the core (could always try building a community sink for this though)

Thanks for the note! `WriteTo.Providers()` doesn't bring in support for the MEL configuration system, so this is expected. You can get finer-grained control of individual providers if you can move...