line 39, it says the FILE_NAME is first parameter, PKG_DEPS is second and CLASS_NAME is only third. Here it says provide it as the second parameter, which does not work.

If i only call
setup-ros-node my_node, PKG_DEPS is "", which is expected

However, if i call
setup-ros-node my_node MyFirstNode, the class name is still being guessed.

Below, I removed the PKG_DEPS argument, as it is not used anywhere.

you are right! I have fixed nos using PKG_DEPS. Can you check again?

The thing is that as we are using positional arguments, you have to provide empty second argument to set the third.

then, if i want to define a special class name, I have to know to that the second parameter should be empty, which seems convoluted.

For example, now running:

setup-ros-node my_node MyFirstNode

places <depend>MyFirstNode</depend> in the package.xml.

In my opinion, this script is trying to do too much.

This script should generate the required files and boilerplate for CMakeLists.txt and ROS parameters. That is the most tedious part, as I see it.

Adding dependancies should be done by the user, manually, as we usually add dependancies anyways while developing the node.

I suggest we remove adding package dependancies except <build_depend>generate_parameter_library</build_depend>, and make the custom node name parameter $2, in the remote case the class name will not correspond to the file name, but CamelCase.

In the spirit of my previous comment, can we remove the is the package already configured? prompt?

when using create-new-package, we are already "configuring the package" by setting up some CMakeLists.txt code.

We can just make this script add dependancy to generate_parameter_library, link the new files and call it a day? This prompt also adds some unecessary complexity, in my opinion.

We can always expand the functionality later, as we use the script.

the functionality about adding the is already configured is when you are adding a second node to already setup package. Not wehn you configure your package with create-new-package.

We can remove adding dependecies, but more the simplicity then chaning the interface. The documentation is clear that if you want to add a custom class (Which is rearly the case to be honest) then you have to provde all three arguemnts. That is how bash works.

On the other hand, I am lazy, and would rather do small fixes later for the dependecies then have to add them manually. We are talking here not about 100% dependecy coverage when you gnerate your file, but more about initial dependecies.

head and tail commands are having trouble parsing the expanded string, I'm getting these warnings:

tail: invalid number of lines: ‘+’
head: unrecognized option '--1'
Try 'head --help' for more information.
tail: invalid number of lines: ‘+’
tail: invalid number of lines: ‘+’
tail: invalid number of lines: ‘+’

This is happening both when $package_configured is no or yes

Is this working as expected on your machine?

What is the initial state of your package when testing this?

I tried adding a my_node in a package where I already have one node set up.

when selecting package_configured = yes, the script deletes my whole CmakeLists.txt and writes only

# Add my_node library related compile commands
generate_parameter_library(my_node_parameters
  src/my_node.yaml
)
add_executable(my_node src/my_node.cpp)
target_include_directories(my_node PRIVATE
  "$<BUILD_INTERFACE:${PROJECT_SOURCE_DIR}/include>"
  "$<INSTALL_INTERFACE:include/${PROJECT_NAME}>")
target_link_libraries(my_node my_node_parameters)
ament_target_dependencies(my_node ${THIS_PACKAGE_INCLUDE_DEPENDS})

ament_export_libraries(
  my_node
)

This is not happening when selecting package_configured = no in the same package. In that case, it adds the above text to the existing CmakeLists.txt

OK, this is a bug then. I didn't tested it at already configured packages. I just copy paseted some thing so we have it.

single quotes are required here

why? I want that ${PROJECT_NAME} is parsed to the string. so this should work