How would I integrate this library with Wagmi/React?

[zkSoju]

Hi there!

Curious what would be the best approach to utilizing this library with Wagmi React hooks? (https://github.com/tmm/wagmi/) I was following an active PR about passing a signer to the Seaport constructor, but I couldn't figure out how to expose that in Wagmi.

I think an option is utilizing this repos utility functions to create a custom hook library with wagmi under the hood.

[sunwrobert]

Is there a more specific aspect that you need help figuring out? Not familiar with Wagmi so not sure what exactly is the issue here. Maybe an example use case and how you would want to use it would be best here.

[zkSoju]

Hm, I was under the assumption that signTypedData would be provided for the most part for custom signers. What type of signer are you providing and how would it normally sign typed data?

The signer is supplied as an ethers.Signer by wagmi (https://wagmi.sh/docs/hooks/useSigner), but it doesn't seem to supply _signTypedData that's shown here: https://docs.ethers.io/v5/api/signer/#Signer-signTypedData

[sunwrobert]

Are you using it in the context of the browser? It's likely that it actually has signTypedData provided. I would try ignoring the type there and seeing if it works, and then maybe we can adjust the type accordingly in seaport-js

[zkSoju]

Hi, is there an example use case of this?

[BravoNatalie]

I'm with the same problem, and it works when you ignore the error like this:

 //@ts-ignore
const seaport = new Seaport(signerFromWagmi)

[zkSoju]

I'm with the same problem, and it works when you ignore the error like this:

 //@ts-ignore
const seaport = new Seaport(signerFromWagmi)

If you're having issues still, I followed this implementation - it works well:
https://github.com/jeff0723/3card/blob/main/packages/web/src/providers/SeaportProvider.tsx

It works well, just make sure to try catch executeAllActions because there are missing signer errors when transactions get denied.