6 replies

Best practices - defining types when lib doesn't export the type

I'm writing a hook that wraps a transaction from another library.
The library returns a Promise<SendTransactionResult>, but SendTransactoinResult is not exported from the library.
I'm writing a handler for the promise but I'm struggling with what the best practice would be for defining the type that this callback should expect.

 /*...inside hook...*/
// my function
const afterContractWrite = useCallback(
  (result: <HowWouldYouDefineThisType?>) => {
    onSettled?.();
    return result.wait();
  },
  [onSettled]
); 

//this method returns a Promise<SendTransactionResult> but the type is not exported from the lib so I can't just import it.
writeAsync?.() 
      .then(afterContractWrite)

 /*...inside hook...*/
// my function
const afterContractWrite = useCallback(
  (result: <HowWouldYouDefineThisType?>) => {
    onSettled?.();
    return result.wait();
  },
  [onSettled]
); 

//this method returns a Promise<SendTransactionResult> but the type is not exported from the lib so I can't just import it.
writeAsync?.() 
      .then(afterContractWrite)

How would you handle this?

TTC

Theo's Typesafe Cult•4y ago•

6 replies

CuriouslyCory

Best practices - defining types when lib doesn't export the type

 /*...inside hook...*/
// my function
const afterContractWrite = useCallback(
  (result: <HowWouldYouDefineThisType?>) => {
    onSettled?.();
    return result.wait();
  },
  [onSettled]
); 

//this method returns a Promise<SendTransactionResult> but the type is not exported from the lib so I can't just import it.
writeAsync?.() 
      .then(afterContractWrite)

 /*...inside hook...*/
// my function
const afterContractWrite = useCallback(
  (result: <HowWouldYouDefineThisType?>) => {
    onSettled?.();
    return result.wait();
  },
  [onSettled]
); 

//this method returns a Promise<SendTransactionResult> but the type is not exported from the lib so I can't just import it.
writeAsync?.() 
      .then(afterContractWrite)

How would you handle this?

Best practices - defining types when lib doesn't export the type

Similar Threads

Best practices - defining types when lib doesn't export the type

Similar Threads

Similar Threads

Similar Threads