Allow generating messages services in an action folder

[sloretz]

Feature request

Feature description

rosidl_typesupport_fastrtps_c and rosidl_typesupport_fastrtps_cpp need to allow generating messages and services in an action folder and namespace

Implementation considerations

The service templates would need to change to allow service definitions to live in the .actions folder

rosidl_typesupport_fastrtps/rosidl_typesupport_fastrtps_c/resource/srv__type_support_c.cpp.em

Lines 27 to 28 in 7263c08

	#include "@(spec.pkg_name)/srv/@(get_header_filename_from_msg_name(spec.srv_name + '_Request'))__rosidl_typesupport_fastrtps_c.h"
	#include "@(spec.pkg_name)/srv/@(get_header_filename_from_msg_name(spec.srv_name + '_Response'))__rosidl_typesupport_fastrtps_c.h"

rosidl_typesupport_fastrtps/rosidl_typesupport_fastrtps_cpp/resource/srv__type_support.cpp.em

Lines 20 to 22 in 7263c08

	#include "@(spec.pkg_name)/srv/@(get_header_filename_from_msg_name(spec.srv_name))__struct.hpp"
	#include "@(spec.pkg_name)/srv/@(get_header_filename_from_msg_name(spec.srv_name + '_Request'))__rosidl_typesupport_fastrtps_cpp.hpp"
	#include "@(spec.pkg_name)/srv/@(get_header_filename_from_msg_name(spec.srv_name + '_Response'))__rosidl_typesupport_fastrtps_cpp.hpp"

connects to ros2/rosidl#301

[sloretz]

Actually I'm not sure about this issue. If actions are implemented in rcl, why should an rmw specific typesupport need to be aware of them? It seems like the only thing to do here would be allow generating services in a folder other than srv so that rosidl_generate_c could invoke this generator with services and messages in an action namespace.

Edit: Changed this issue to say as much