Francesco Ceccon
Francesco Ceccon
Agree with this. We should add the following hooks: * `useProviderCall` that has the same behaviour as the current call hook, but calls `provider.callContract` * `useProviderInvoke` that uses `provider.invokeFunction`
Another way to do this, change `useStarknetCall` to: ```ts function useStarknetCall({ contractOrAddress }: { contractOrAddress?: string | Contract }) ``` If it's a `Contract`, then the behaviour is the same...
The idea is to add a set of `onAccepted`, `onAcceptedOnL1` etc arguments to the hook. Every time the tx status changes, the user-provided callback is called.
That sounds good! It looks like it can be done together with #174.
This is super useful combined with cypress to have end-to-end tests.
This can be done with `moq.ts`, so no need to reinvent the wheel.
I agree with this. The hook should also listen for network changed events on the wallet to keep the current network updated.
I think the best way forward is to continue improving on the connectors interface we have. There should be a way to list StarkNet wallets installed by the user (for...
/cc @tarrencev @janek26 @avimak