Feature/removing enums and using ros message values instead #67
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
sanazfth
requested review from
JWhitleyWork,
icolwell-as,
jilinzhouas and
shan-as
Can you link the PR that is making that addition? |
JWhitleyWork
force-pushed
the
feature/removing_enums_and_using_ROS_message__values_instead
branch
from
fe1647a to
1ea3e11
Compare
|
CI fixed. |
jilinzhouas
approved these changes
Nov 27, 2019
JWhitleyWork
deleted the
feature/removing_enums_and_using_ROS_message__values_instead
branch
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.
adding turn_hazards to PacmodCmd.msg astuff_sensor_msgs#48