Consistency codebase refactor

[carletex]

Let's do some refactoring to have a more consistent codebase:

• It seems that we are more inclined to use types without T prefix. Let's unify for consistency. Refactor: types/interfaces #627
• 0x${string} to viem's Address? [WIP @sverps ]
• TS: interfaces -> types Refactor: types/interfaces #627
• JSDoc tweaks: see Refactor: types/interfaces #627 (comment)

Check TS guide: #232

What else? cc @technophile-04 @rin-st @sverps

[rin-st]

• TS: interfaces -> types
• components/scaffold-eth/Contract utilsContract.tsx, utilsDisplay.tsx -> utils.ts. Also refactor it, for example move getParsedError to utils/scaffold-eth
• remove barrels?)

[carletex]

Updated OP with new stuff. Also opened #627

I also think we should have all the desired consistency documented up somewhere (with conclusions from #232 too).

Not sure where the best place could be: Github wiki? SE-2 docs -> contributing?

---

remove barrels?

Yep, this is an interesting discussion too. I remember seeing some issues in the NextJS 14 migration with HMR.

[technophile-04]

Not sure where the best place could be: Github wiki? SE-2 docs -> contributing?

Didn't knew about Github Wiki! I think it looks a fare place 🙌

remove barrels?

Yep, this is an interesting discussion too. I remember seeing some issues in the NextJS 14 migration with HMR.

I am kind of 60%(remvoing barrels) and 40% keeping them because I think in new Next version there is option to mark barrels file and optimize them => https://vercel.com/blog/how-we-optimized-package-imports-in-next-js but don't know if it actually work a.....100% assured solution will be removing barrels files

• JSDoc tweaks: see Refactor: types/interfaces #627 (comment)

Is anybody already working on this TODO ? Would love to tackle it 🙌

[sverps]

I'm picking up the address type stuff