fix warning message #371
Merged
fix warning message #371
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
Signed-off-by: Alaa El Jawad <ejalaa12@gmail.com>
ahcorde
approved these changes
Mar 10, 2023
|
CI failure appears unrelated. Merging! |
azeey
pushed a commit
to azeey/ros_gz
that referenced
this pull request
Apr 28, 2023
Signed-off-by: Alaa El Jawad <ejalaa12@gmail.com>
azeey
pushed a commit
that referenced
this pull request
May 1, 2023
Signed-off-by: Alaa El Jawad <ejalaa12@gmail.com>
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.
馃 Bug fix
Summary
The warning message had the ros_type and gz_type swapped out, which woud throw warnings that looked like this:
The line in the code were swapped out. This PR just fixes that
Checklist
codecheckpassed (See contributing)