Currently nevermore strategy options are specified directly in the calls to createExecutorStrategy or createSettlementSequence.
This mean that a new strategy is always created by those calls, so it's impossible to share a strategy between both the executor API and the settlement API, or multiple instances of each.
It should therefore be trivial to lift the common creation logic, and expose a further method call that allows reuse of the same strategy. This might include e.g. executors that share only the last part of a strategy pipeline, and specialise the earlier strategies.
Currently
nevermorestrategy options are specified directly in the calls tocreateExecutorStrategyorcreateSettlementSequence.This mean that a new strategy is always created by those calls, so it's impossible to share a strategy between both the
executorAPI and thesettlementAPI, or multiple instances of each.Under the hood both implementations call createStrategyFromOptions.
It should therefore be trivial to lift the common creation logic, and expose a further method call that allows reuse of the same strategy. This might include e.g. executors that share only the last part of a strategy pipeline, and specialise the earlier strategies.