Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Address the logging test failures in #148
A lot of changes so I'm opening a PR instead of just pushing to
3_to_4
branch.The reason that that empty path test was failing, was because we don't allow the user to use
<path>
, but internally we inject<path>
for the plugin to read. When the test specifies<path>
in an SDF, it's ignored - which means if it exists, it isn't removed. Then whenLogRecord
sees the tag, it doesn't know whether that<path>
came from the injection (legit) or the user (or test in this case, not legit). The plugin just goes ahead and records to it, even when it came from the user.To avoid that confusion, we can either check for user-specified
<path>
and strip it before adding the legit one (70c79be), which I then realized looks silly, so I just changed the tag name we inject to<record_path>
. Now there won't be confusion. I added a TODO item to put it in aComponent
.I also realized a lot of tests needed to be updated so that they aren't using the removed
<path>
feature. Two are removed because we aren't allowing SDF<path>
anymore, so those two cases are no longer different from the existing ones.P.S. I’m seeing a lot of clang_tidy warnings in many files, I don’t know if we want to fix them as we’re doing
3_to_4
.