-
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
ExceptionLayoutRenderer - Separator with basic Layout support #4583
Conversation
7a5e32b
to
302e2b8
Compare
Kudos, SonarCloud Quality Gate passed! |
@304NotModified Unless you are completely against this, then I would like commit and proceed with adding basic layout support for the other seperators. So NLog 5.0-preview2 can get out. |
For the exception layout renderer? That sounds fine to me. |
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.
This PR is a bit hard too review (it's large), but I think its fine
Was thinking to also fix:
|
Ah OK, good idea :) |
Resolves #2249, so it is possible for users to specify
${newline}
in the NLog.config for the Separator-property.Also changes property-parsing so it work for LayoutRenderer-string-options, so it is consistent with NLog-Target-options and NLog-Layout-options.
ExceptionLayoutRenderer
is very special since it allows users to override the rendering-methods for the individual parts. So the backing-field remains a string to ensure predictable behavior for the users, that wants to override rendering-methods.