📝 docs: organize config.mts

[Sabnock01]

• Organizes the actions in alphabetical order (viem.sh also uses alphabetical ordering of actions)
• Creates and adds missing pages to index (will implement those once this is merged; plenty of empty pages already exist)
• Fixes a typo in the sidebar for simulateWithdrawERC20

Let me know if we prefer another name to the General category under Utilities for functions like resolveL1OpStackContractAddress.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
op-viem-site	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 20, 2023 5:16am

[Sabnock01]

Decided writeOpStackL1 and resolveL1OpStackContractAddressshould be included in this PR.

[wilsoncusack]

Thanks for this! I was unsure if we wanted to expose writeOpStackL1, I think it is not currently exported. Got some feedback the name was confusing and there was some debate if this function is worth having (I currently think it probably is). Any thoughts @Sabnock01 ?

[wilsoncusack]

I think this is internal and we don't need to export

[Sabnock01]

Thanks for this! I was unsure if we wanted to expose writeOpStackL1, I think it is not currently exported. Got some feedback the name was confusing and there was some debate if this function is worth having (I currently think it probably is). Any thoughts @Sabnock01 ?

I am fine with exporting writeOpStackL1 and leaving resolveL1OpStackContractAddress as internal.

[wilsoncusack]

Thanks for this! I was unsure if we wanted to expose writeOpStackL1, I think it is not currently exported. Got some feedback the name was confusing and there was some debate if this function is worth having (I currently think it probably is). Any thoughts @Sabnock01 ?

I am fine with exporting writeOpStackL1 and leaving resolveL1OpStackContractAddress ad internal.

ok, let's do that then. I also wonder if writeOpStackL1Contract might be a more clear naming.

[Sabnock01]

Thanks for this! I was unsure if we wanted to expose writeOpStackL1, I think it is not currently exported. Got some feedback the name was confusing and there was some debate if this function is worth having (I currently think it probably is). Any thoughts @Sabnock01 ?

I am fine with exporting writeOpStackL1 and leaving resolveL1OpStackContractAddress ad internal.

ok, let's do that then. I also wonder if writeOpStackL1Contract might be a more clear naming.

I think it is. Want to rename to both writeOpStackL1Contract and writeOpStackL2Contract?

[wilsoncusack]

@Sabnock01 I am open to this but let's make it a different PR. Maybe this one can just be the reorg and we can punt on writeOpStackL1 and plan to not have docs or export resolve...