Update docs with Wagmi v2 changes

[Pabl0cks]

Creating this draft to start working on #60 to adapt docs to all changes involved with SE2 Wagmi v2 migration

• Update wagmi docs links to v2
• Update viem docs links to v2
• Update custom hooks names, params and examples to wagmi v2
• Update recipes

Closes #60

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
scaffold-eth-2-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 15, 2024 5:27pm

[Pabl0cks]

Maybe add a small section about upgrading a Wagmi v1 SE-2 project to a Wagmi v2 SE-2 project?

I think Damu's idea in #60 can be helpful for people wanting to migrate to latest SE-2 version, without having to check all details of wagmi v2 migration.
Let me know if you think it's interesting and I'll prepare a draft version for that guide 🙌, we could add it at the end of hooks menu.

Some doubts I had when I was documenting the changes:

• In useScaffoldWriteContract doc I'm instanciating writeContractAsync into writeYourContractAsync, not sure if it's the right practice for the docs.
• In recipes (WagmiContractWriteWithFeedback and WriteToContractWriteAsyncButton) I was not sure about putting the writeContractAsyncWithParams into the event handler or not. Did not put it for simplicity of the example, but don't know if it's a good practice for a "real world" example

Hope I haven't missed any changes, and that my explanations are not terrible 😅

[technophile-04]

TYSM @Pabl0cks !! This is really great !!!

Just pushed a few commits tried keeping them atomic so its easy to read, mainly revolving around :

1. Distinguishing that contract interaction args are now passed to writeContractAsync instead of useSWC eg: 38d8085, d0c172a
2. Wrapping writeContractAsync inside try/catch its important we mention this, earlier it not imp but after Fix useScaffoldContractWrite so it properly throws errors scaffold-eth-2#758 you should do it.
   • EG: Austin getting unhandled error on Next page (bottom left of his page) since he didn't wrap the function

I think this is nicely ready to merge along with scaffold-eth/scaffold-eth-2#700 🙌

[Pabl0cks]

Thanks for the awesome review @technophile-04!!

Love all the improvements and learnt from the fixes 🙌

[technophile-04]

Merging this, we already merged scaffold-eth/scaffold-eth-2#700

Tysm @Pabl0cks again !!