What needs to be done?
Commands should follow interface segregation to make the engine plugin-friendly. Current HistoryLevelSetupCommand is a final class without parent interface for ProcessEngineConfiguration.historyLevelCommand field, which makes it impossible to adjust in plugins
Additional context
Current configuration schemaOperationsCommand and bootstrapCommand fields and commands follow proper typing
In my opinion, the whole command pattern design with its implications (such as plugin friendly commands typing & configuring) should be described in a document like adr despite the fact that it was inherited from Camunda 7
What needs to be done?
Commands should follow interface segregation to make the engine plugin-friendly. Current
HistoryLevelSetupCommandis a final class without parent interface forProcessEngineConfiguration.historyLevelCommandfield, which makes it impossible to adjust in pluginsAdditional context
Current configuration
schemaOperationsCommandandbootstrapCommandfields and commands follow proper typingIn my opinion, the whole command pattern design with its implications (such as plugin friendly commands typing & configuring) should be described in a document like adr despite the fact that it was inherited from Camunda 7