Now that we put out a 3.0.0b1 beta release for cmd2, much of our automatic CI/CD is failing due to unsatisfiable requirements related to the cmd2-ext-test plugin.
Regardless of the path forward, the current situation we have where testing cmd2 requiring a plugin which itself depends on cmd2 is an abomination of circular dependency that needs to end. A plugin which depends on cmd2 should not IMO be part of the main repository.
I see three general possible paths forward:
- Deprecate the
cmd2-ext-test plugin, delete the code for it, and include the mixin class in our isolated tests
- Move the
cmd2-ext-test plugin to a separate repository and modernize it so it works with cmd2 3.x
- Bake the mixin class into
cmd2 itself so it is available to all users and deprecate the plugin
One option is to document for users how they can create this mixin tests for their own testing ease.
Now that we put out a
3.0.0b1beta release forcmd2, much of our automatic CI/CD is failing due to unsatisfiable requirements related to thecmd2-ext-testplugin.Regardless of the path forward, the current situation we have where testing
cmd2requiring a plugin which itself depends oncmd2is an abomination of circular dependency that needs to end. A plugin which depends oncmd2should not IMO be part of the main repository.I see three general possible paths forward:
cmd2-ext-testplugin, delete the code for it, and include the mixin class in our isolated testscmd2-ext-testplugin to a separate repository and modernize it so it works withcmd23.xcmd2itself so it is available to all users and deprecate the pluginOne option is to document for users how they can create this mixin tests for their own testing ease.