refactor: migrate adapter service to api #117
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.
This PR refactors the Adapter to remove the running service component. The goal behind this is to remove the channel communication between the adapter and other components, instead, Adapter now acts as an API. The Adapter API currently is a single nameless trait with all functionality combined, this change will allow splitting that API out into relevant components to better isolate functionality. For now though, this just moves the entire API into a temporary trait called
AdapterApi
, in future PR's,adapter/
will becomestate/
and the relevant functionality will be broken out.Apart from the
AdapterApi
and channel removal, all other changes are mechanical, just propagating the change through the codebase.Some changes that occurred during this refactoring:
.../adapter/api.rs
to replace the only meaningful runtime component of adapter.S
parameter is added anywhere Adapter used to be relied on.++increment
behaviourincrement++
AdapterApi
is now strongly typed, so the rpc.rs API now does proper verification of accounts in the right place.AdapterApi