[#21,#24] Replace rodsLog, inline code where appropriate - #36
Conversation
|
Will review once this is out of draft. |
MartinFlores751
left a comment
There was a problem hiding this comment.
PR should be good to review, will pull out of draft. My comment is on the part that I need to update still. Will need eyes on the inline code. I'm not sure how generous I should be with the keyword.
MartinFlores751
left a comment
There was a problem hiding this comment.
Live review with @korydraughn.
|
Tests are passing so far. Things are looking good. I assume we're waiting for tests to pass and then we'll be ready to squash. You agree? |
Yep. Everything's been addressed, so it's just waiting for the tests. |
|
After we get this PR in, all that's left to do is ...
|
|
All of the tests passed. Take a look at the clang-tidy report if you haven't already. See if we can hammer those out. |
korydraughn
left a comment
There was a problem hiding this comment.
Looks good to me.
After you make the change, squash to taste.
|
Squashed. |
|
Did a quick edit to commit message. |
This commit adds a common logging category for policy composition plugins. The plugins were updated to use this new logger as well. This commit also contains several fixes: - Fixing `.dump(...)` calls to handle invalid Unicode sequences - Adding additional details, such as func `__func__`, to logs - Fixing includes, macro redefinition, and other tidy issues
|
Pounded. |
Issue quick links: #21, #24
This PR replaces rodsLog with the newer logger under
policy_composition_category. This PR also addsinlinewhere appropriate to the policy comp framework library.