I am trying to understand the recommended workflow or best practices for plugin development and finding it a little awkward.
First - Following from your getting started guide, I run openc3.bat cli generate plugin BOB followed by cd openc3-cosmos-bob and openc3.bat cli generate target BOB The result from these two is: .\openc3.bat : The term '.\openc3.bat' is not recognized as the name of a cmdlet, function, script file, or operable program. Which makes sense because there is no such shell script in bobs plugin. Is there supposed to be?
Second - Is the recommended workflow for plugin development to:
1. Generate plugin inside cosmos project
2. Move plugin out of project source, into its own repo and develop there
3. Upload either with admin console or load utility in openc3 batch script, assuming this scriptis present in plugin root
Or is it to generate plugin, develop and load from the openc3 project and use the project source files as the sole repo to track
I am trying to understand the recommended workflow or best practices for plugin development and finding it a little awkward.
First - Following from your getting started guide, I run
openc3.bat cli generate plugin BOB
followed bycd openc3-cosmos-bob
andopenc3.bat cli generate target BOB
The result from these two is:.\openc3.bat : The term '.\openc3.bat' is not recognized as the name of a cmdlet, function, script file, or operable program.
Which makes sense because there is no such shell script in bobs plugin. Is there supposed to be?Second - Is the recommended workflow for plugin development to:
Or is it to generate plugin, develop and load from the openc3 project and use the project source files as the sole repo to track