Codecov Report

Merging #3298 into dev will increase coverage by <1%.
The diff coverage is 85%.

@@          Coverage Diff           @@
##             dev   #3298    +/-   ##
======================================
+ Coverage     80%     80%   +<1%     
======================================
  Files        356     356            
  Lines      28077   28123    +46     
  Branches    3739    3753    +14     
======================================
+ Hits       22485   22551    +66     
+ Misses      4488    4481     -7     
+ Partials    1104    1091    -13

Thanks for the PR,

but i'm afraid it won't change the NLog API viewpoint, mentioned in #2496 (comment)?

If we also add SetProperty, next to WithProperty, do you think that is OK? (from viewpoint API design)

@304NotModified Added a SetProperty method for updating the current Logger object-instance.

Cool!

Need to check it in depth, but I think I will merge it soon :)

Docs added here: https://github.com/NLog/NLog/wiki/EventProperties-Layout-Renderer

Updated the docs a little so the difference between WithProperty and SetProperty is clearer. Making the trap-door hidden in SetProperty a little more visible.

It's not a trap but a feature :)

Updated it with a 2nd log. The set is really useful is some cases (e.g when you get more context along the way)

The set is really useful is some cases (e.g when you get more context along the way)

Not when having the global NLog Logger-cache where multiple locations are referencing the same Logger-object, and then one location suddenly decides to call SetProperty (can become a surprise for everyone else)

It's not suddenly? It's by (logger) name.

Buy anyway, I'm curious when we will implement WithProperties and ClearProperty :p

(Maybe nice with default interfaces - c# 8)

It's not suddenly? It's by (logger) name.

Not sure I understand. There is no guarantee that two isolated locations doesn't call GetLogger() with the same name. When one of the isolated locations calls SetProperty then it will affect the other.

Could also be two threads allocating their isolated controller of the same class, then the two controller-classes will be sharing the same Logger-object (Independent of using static Logger-variable, but just because it calls GetCurrentClassLogger). When one thread starts to call SetProperty then it will affect the Logger on the other controller-instance.

That is why I prefer WithProperty because it doesn't give you surprises.