workflow: Reduce direct dependencies

[andrewwormald]

The idea here is to clarify what the main package uses in terms of dependencies and provide clarity of what each adapter brings. This allows for the user to not have indirect dependencies from adapters that it's not using such as kafka if not using kafka or reflex if not using reflex

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[echarrod]

Downside of this would be if we end up doing semantic versioning (rather than just having users update their digest), the sub-modules would all need to be managed and released separately. I would like to do this eventually for nearly all our modules.

And the benefit of this is that users won't import as many indirect dependencies when they use one of these?

Just considering the trade-off

[andrewwormald]

Downside of this would be if we end up doing semantic versioning (rather than just having users update their digest), the sub-modules would all need to be managed and released separately. I would like to do this eventually for nearly all our modules.

And the benefit of this is that users won't import as many indirect dependencies when they use one of these?

Just considering the trade-off

Yeah the main thing is that example and adapters are not part of the workflow module. The adapters themselves can exist as their own modules not just packages of the workflow module. They themselves can have their own versioning but will always need to implement the specification that the workflow module dictates.