In case the metadata.json file is not yet created I opted to create it automatically to make it easy for the user.
Other option would be to show an error and guide user to create the file first. Or add information to robotEntry type to check if metadata file is there and then we can show it based on that. But this would make the robot listing slower if a filesystem action needs to be always done to check if file is there when listing the available actions.
I also added the fix for build and publish command to find the correct input dir if there are multiple action packages in the workspace.
In case the metadata.json file is not yet created I opted to create it automatically to make it easy for the user. Other option would be to show an error and guide user to create the file first. Or add information to robotEntry type to check if metadata file is there and then we can show it based on that. But this would make the robot listing slower if a filesystem action needs to be always done to check if file is there when listing the available actions.
I also added the fix for build and publish command to find the correct input dir if there are multiple action packages in the workspace.