sov-stf-runner
should not depend on modules
#991
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
sov-stf-runner
suppose to be independent from module system.This PR solves this by doing following things:
sov-modules-api
to direct import fromsov-rollup-interface
FiFoStrictBatchBuilder
tosov-sequencer
RollupConfig
now do not depend on concreteStorageConfig
, but it is generic instead.sov-modules-api
was dependent onsov-sequencer
only forto_jsonrpsee_error_object
function. So it got moved tosov-modules-api
, sincesov-sequencer
already depends on it. And for ledger_rpc it is copied, to avoid bringing wholesov-modules-api
dependency.Testing
Existing tests are passing
Docs
No updates in documentation