Describe the bug
When using TransactionUtils and passing start/end block, their types are defined as number, but return type for block property is bigint, so they are not compatible. If you do types casting block as unknown as number - then bigint is passed and can't be serialised in subgraph query
To Reproduce
Steps to reproduce the behavior:
- Get some tx using
TransactionUtils.getTransactions
- Use
tx.block as startBlock filter in consequent TransactionUtils.getTransactions call
- See TS error
Expected behavior
Types are correct for filters and bigint can be used (i.e. block numbers have correct types and serialized correctly before passing to subgraph query)
Screenshots
Describe the bug
When using
TransactionUtilsand passing start/end block, their types are defined asnumber, but return type forblockproperty isbigint, so they are not compatible. If you do types castingblock as unknown as number- thenbigintis passed and can't be serialised in subgraph queryTo Reproduce
Steps to reproduce the behavior:
TransactionUtils.getTransactionstx.blockasstartBlockfilter in consequentTransactionUtils.getTransactionscallExpected behavior
Types are correct for filters and
bigintcan be used (i.e. block numbers have correct types and serialized correctly before passing to subgraph query)Screenshots
