[ANCHOR-916] Put Horizon behind interface #1624
Conversation
lijamie98
force-pushed
the
feature/anchor-916-put-horizon-behind-interface
branch
from
f5dca97 to
463ae5b
Compare
| * @return The transaction response. | ||
| * @throws NetworkException | ||
| */ | ||
| TransactionResponse submitTransaction(Transaction transaction) throws NetworkException; |
There was a problem hiding this comment.
TransactionResponse is Horizon's submitTransaction response. RPC's sendTransaction returns a SendTransactionResponse which only contains the transaction hash and its status. We will need to call getTransaction to fetch the transaction afterward. The schemas are not the same. Should we create a new type to encapsulate the transaction submission responses?
| import org.stellar.sdk.responses.TransactionResponse; | ||
| import org.stellar.sdk.responses.operations.OperationResponse; | ||
|
|
||
| public interface LedgerApi { |
There was a problem hiding this comment.
SEP-45 uses transaction simulation which is only available in RPC. How do we plan to expose RPC-specific methods in the interface?
| * @param stellarTxnId The Stellar transaction ID. | ||
| * @return The operations for the transaction. | ||
| */ | ||
| List<OperationResponse> getStellarTxnOperations(String stellarTxnId); |
There was a problem hiding this comment.
OperationResponse is Horizon's getOperation response. If we use RPC, we must parse the operations from the transaction envelope. Should we create a new type to encapsulate the operation response?
| private AccountEntry fetchAccountEntry(String account) throws IOException { | ||
| // TODO: Implement this method | ||
| return null; | ||
| // GetLedgerEntriesResponse response; |
| @@ -71,4 +115,9 @@ public List<OperationResponse> getStellarTxnOperations(String stellarTxnId) { | |||
| .execute() | |||
| .getRecords(); | |||
| } | |||
|
|
|||
| @Override | |||
| public TransactionResponse submitTransaction(Transaction transaction) throws NetworkException { | |||
There was a problem hiding this comment.
Do we only submit transactions in tests? It should not be part of the interface if that's the case.
| } | ||
|
|
||
| /** Increments sequence number in this object by one. */ | ||
| public void incrementSequenceNumber() { |
|
Also, for the branch name. I think we typically call long-lived feature branches |
Description
LedgerApiinterfaceContext
Testing
./gradlew testDocumentation
N/A
Known limitations
N/A