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.
Pull Request
Closes: PRO-889
Checklist
Please conduct a thorough self-review before opening the PR.
Summary
Split
RpcSigningClient
intoEthRpcSigningClient
(capable of signing/broadcasting) andRpcSigningClient
(no signing). Similarly, split the traits intoEthRpcApi
andEthSigningRpcApi
. Similary, for I split the "retry" traits intoEthersRetrySigningRpcApi
andEthersRetryRpcApi
. NowEthersRetryRpcClient
is generic over the rpc client so that if the inner client implementsEthSigningRpcApi
, then the retry client implementsEthersRetrySigningRpcApi
. The result is thatEthersRetryRpcClient<EthRpcSigningClient>
can do everything thatEthersRetryRpcClient<EthRpcClient>
plus broadcasting. Finally, I changed some of the interfaces to only require non-signing client (though a signing would work just fine) and the tracker uses a non-signing client.I recommend reviewing this PR commit by commit.