Sugestion for a new grammar for the message specifications#197
Draft
ipa-nhg wants to merge 2 commits intoipa320:mainfrom
Draft
Sugestion for a new grammar for the message specifications#197ipa-nhg wants to merge 2 commits intoipa320:mainfrom
ipa-nhg wants to merge 2 commits intoipa320:mainfrom
Conversation
f84a682 to
c9fb502
Compare
39190a9 to
5837d31
Compare
This file contains hidden or 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
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.
These changes are from @ipa-rwu
‼️ Code has to be re-generated before merge ‼️
This PR include the remaining commits from #194
This suggestion requires a major discussion. Initially, the idea was to keep the .msg format for the definition of the specifications, for example:
This approach will significantly lower the entry barrier for the ROS community. As the original code is:
std_msgs/ColorRGBA.msg
std_srvs/Trigger.srv
With this PR you are proposing: