Added trigger_joint_command_threshold_enabled_ #106
Conversation
…always sent if the trigger_joint_command_threshold param is not set
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #106 +/- ##
==========================================
- Coverage 77.89% 77.46% -0.44%
==========================================
Files 6 6
Lines 457 457
Branches 46 45 -1
==========================================
- Hits 356 354 -2
- Misses 70 72 +2
Partials 31 31
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
MarqRazz
left a comment
There was a problem hiding this comment.
Thanks for taking the time to clean this up!
christophfroehlich
left a comment
There was a problem hiding this comment.
This could also be done by just changing the default value to a negative one (-1 for example), without the need of adding another member variable?
|
Yes sir. My bad 😔. I'll change it |
|
This PR is stale because it has been open for 45 days with no activity. Please tag a maintainer for help on completing this PR, or close it if you think it has become obsolete. |
Added trigger_joint_command_threshold_enabled_ to ensure messages are always sent if the trigger_joint_command_threshold param is not set.