[jsk_topic_tools] Fixed use_warn option #1592
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
furushchev
requested changes
Aug 2, 2018
| @@ -61,7 +61,7 @@ namespace jsk_topic_tools | |||
| if (pnh_->hasParam("use_warn")) { | |||
| pnh_->getParam("use_warn", use_warn); | |||
| } | |||
| if (use_warn) | |||
| if (use_warn == false) | |||
| { | |||
| diagnostic_error_level_ = diagnostic_msgs::DiagnosticStatus::ERROR; | |||
There was a problem hiding this comment.
+1 for swapping ERROR and WARN is preferred for readability instead of use_warn == false.
There was a problem hiding this comment.
OK. I revised it based on review
|
Please merge this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In this PR,
default of diagnostic error level have been mistakenly changed to
warn.This PR fixes warn level.