-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JsonLayout - Don't mark ThreadAgnostic when IncludeMdc or IncludeMdlc is enabled #2164
JsonLayout - Don't mark ThreadAgnostic when IncludeMdc or IncludeMdlc is enabled #2164
Conversation
7ac0108
to
41ff0ca
Compare
@@ -63,7 +63,7 @@ public abstract class Layout : ISupportsInitialize, IRenderable | |||
/// | |||
/// Thread-agnostic layouts only use contents of <see cref="LogEventInfo"/> for its output. | |||
/// </remarks> | |||
internal bool ThreadAgnostic { get; private set; } | |||
internal bool ThreadAgnostic { get; set; } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer to make it protected set
. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well internal is "almost" private so it is more restrictive than protected. You are not allowed to upgrade the setter to protected, so it can be accessed by external classes.
Else the entire property should become protected, and part of the official interface. I don't think this internal optimization detail, should be exposed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant protected internal
. Not sure if that could be set on the setter only.
Its indeed and internal optimization (just makes the intention more clear).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Scratch that, its then protected or internal. Not and
I really prefer this solution :) (reported here: #2109 (comment)) |
If you rebase on the latest master, does sonarqube work then? |
Not that strong with GIT. Can only see one master-branch, and no changes has been made to this for some time, and this PR is branched of that same master. What do you mean? |
Could you do
|
|
Just on mobile, so hopefully no errors
After fixing stuff ( When done
|
Updated it, you need fetch all |
41ff0ca
to
c651f88
Compare
@304NotModified Updated and triggered rebuild |
Codecov Report
@@ Coverage Diff @@
## master #2164 +/- ##
=======================================
+ Coverage 81% 81% +<1%
=======================================
Files 291 291
Lines 20124 20135 +11
Branches 2392 2394 +2
=======================================
+ Hits 16343 16367 +24
Misses 3152 3152
+ Partials 629 616 -13 |
Different solution to the same problem.