fix(type-naming): more expressive types

starknet-io · Nov 5, 2021 · 5277b12 · 5277b12
1 parent 08a2e31
commit 5277b12
Show file tree

Hide file tree

Showing 3 changed files with 8 additions and 5 deletions.
diff --git a/package-lock.json b/package-lock.json
diff --git a/src/starknet.ts b/src/starknet.ts
@@ -2,8 +2,8 @@ import axios from 'axios';
 
 import type {
   AddTransactionResponse,
-  Call,
   CallContractResponse,
+  CallContractTransaction,
   CompiledContract,
   GetBlockResponse,
   GetCodeResponse,
@@ -46,7 +46,10 @@ export function getContractAddresses(): Promise<GetContractAddressesResponse> {
  * @param blockId
  * @returns the result of the function on the smart contract.
  */
-export function callContract(invokeTx: Call, blockId?: number): Promise<CallContractResponse> {
+export function callContract(
+  invokeTx: CallContractTransaction,
+  blockId?: number
+): Promise<CallContractResponse> {
   return new Promise((resolve, reject) => {
     axios
       .post(`${FEEDER_GATEWAY_URL}/call_contract?blockId=${blockId ?? 'null'}`, {

diff --git a/src/types.ts b/src/types.ts
@@ -45,7 +45,7 @@ export type InvokeFunctionTransaction = {
   calldata?: string[];
 };
 
-export type Call = Omit<InvokeFunctionTransaction, 'type'>;
+export type CallContractTransaction = Omit<InvokeFunctionTransaction, 'type'>;
 
 export type Transaction = DeployTransaction | InvokeFunctionTransaction;