You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at a launch file tutorial, I was struck by the verbose use of both the PathJoinSubstitution and FindPackageShare substitutions. It would be very easy to simplify this for the end-user with a single FindPackageFile substitution, for example. Is there any reason this wasn't done originally and would such a change be welcomed?
The text was updated successfully, but these errors were encountered:
How appropriate would it be to have a similar feature for Yaml launch files? Just enough capability to allow importing a given launch file from a given package? It would definitely allow for a lot more launch files to be written in Yaml instead of Python.
Feature request
Feature description
Looking at a launch file tutorial, I was struck by the verbose use of both the
PathJoinSubstitution
andFindPackageShare
substitutions. It would be very easy to simplify this for the end-user with a singleFindPackageFile
substitution, for example. Is there any reason this wasn't done originally and would such a change be welcomed?The text was updated successfully, but these errors were encountered: