{"action":"created","issue":{"url":"https://api.github.com/repos/ros2/rosidl/issues/280","repository_url":"https://api.github.com/repos/ros2/rosidl","labels_url":"https://api.github.com/repos/ros2/rosidl/issues/280/labels{/name}","comments_url":"https://api.github.com/repos/ros2/rosidl/issues/280/comments","events_url":"https://api.github.com/repos/ros2/rosidl/issues/280/events","html_url":"https://github.com/ros2/rosidl/issues/280","id":327154864,"number":280,"title":"is there any complete name rules for name of *.msg file and variable in *.msg file when building msg idl ? ","user":{"login":"lxbeyond","id":10123842,"avatar_url":"https://avatars1.githubusercontent.com/u/10123842?v=4","gravatar_id":"","url":"https://api.github.com/users/lxbeyond","html_url":"https://github.com/lxbeyond","followers_url":"https://api.github.com/users/lxbeyond/followers","following_url":"https://api.github.com/users/lxbeyond/following{/other_user}","gists_url":"https://api.github.com/users/lxbeyond/gists{/gist_id}","starred_url":"https://api.github.com/users/lxbeyond/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lxbeyond/subscriptions","organizations_url":"https://api.github.com/users/lxbeyond/orgs","repos_url":"https://api.github.com/users/lxbeyond/repos","events_url":"https://api.github.com/users/lxbeyond/events{/privacy}","received_events_url":"https://api.github.com/users/lxbeyond/received_events","type":"User","site_admin":false},"labels":[{"id":666362408,"url":"https://api.github.com/repos/ros2/rosidl/labels/more-information-needed","name":"more-information-needed","color":"159818","default":false},{"id":113361326,"url":"https://api.github.com/repos/ros2/rosidl/labels/question","name":"question","color":"d876e3","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-05-29T02:57:07Z","updated_at":"2018-05-29T07:03:57Z","closed_at":null,"author_association":"NONE","body":"when I build my msg file, I found some name rules of creating msg file, such as : \r\nrule 1: there should't be any upper-case characters in varialbe name in msg file. for example, \r\n      \"string abc\" is valid,  and \"string aBc\" in invalid.\r\nrule 2: the name of msg file should begin with upper-case characters. for example, msg file name     \r\n      \"Tmpmsg.msg\" is valid, but \"tmpmsg.msg\" is invalid.\r\nso I wonder whether if any complete rules for msg naming which will make me do less trying work when I want to build a correct msg ?"},"comment":{"url":"https://api.github.com/repos/ros2/rosidl/issues/comments/392673589","html_url":"https://github.com/ros2/rosidl/issues/280#issuecomment-392673589","issue_url":"https://api.github.com/repos/ros2/rosidl/issues/280","id":392673589,"user":{"login":"mikaelarguedas","id":6644208,"avatar_url":"https://avatars1.githubusercontent.com/u/6644208?v=4","gravatar_id":"","url":"https://api.github.com/users/mikaelarguedas","html_url":"https://github.com/mikaelarguedas","followers_url":"https://api.github.com/users/mikaelarguedas/followers","following_url":"https://api.github.com/users/mikaelarguedas/following{/other_user}","gists_url":"https://api.github.com/users/mikaelarguedas/gists{/gist_id}","starred_url":"https://api.github.com/users/mikaelarguedas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikaelarguedas/subscriptions","organizations_url":"https://api.github.com/users/mikaelarguedas/orgs","repos_url":"https://api.github.com/users/mikaelarguedas/repos","events_url":"https://api.github.com/users/mikaelarguedas/events{/privacy}","received_events_url":"https://api.github.com/users/mikaelarguedas/received_events","type":"User","site_admin":false},"created_at":"2018-05-29T07:03:57Z","updated_at":"2018-05-29T07:03:57Z","author_association":"CONTRIBUTOR","body":"The design document defining the ROS interfaces is available here: http://design.ros2.org/articles/interface_definition.html\r\n\r\nThe naming rules as well as msg/srv file formatting are detailed in the \"Conventions\" section.\r\n\r\nThe rule 3 you declared above is not part of the conventions: `While a single space is mandatory to separate tokens additional spaces can be inserted optionally between tokens.`.\r\nI just tried on existing msg files and couldn't get them to fail when using multiple spaces between the field type and the field name. Are you sure you added only spaces between them ? Can you provide a msg file that fails for you so that we can reproduce the issue ?"}}
{"actor":{"display_login":"mikaelarguedas"}}