g. nicholas d'andrea

This should also likely include some kind of scenario test for `truffle debug` in a Hardhat project

@elenadimitrova IIRC we ended up needing to revert that PR because of complexities it introduced. I'll re-open this.

We may want to hold off on this until we have @truffle/codec-components, since the absence of that library makes this format more externally-facing than if we had that library.

I'm torn... I really like the simplicity of just using strings everywhere and avoiding the need for custom JSON logic. But yeah, trade-offs... 🤷

> I think @gnidan and I talked about this and decided to fix it but leave it undocumented. Do you still feel the same @gnidan? Yes I still feel this...

Hm this keeps happening to some users periodically. Unfortunately the team is out of office this week and we can't help diagnose this until we return. In the meantime, please...

Maybe we should make it an option for `truffle init`, like `truffle init --with-migrations`. But yeah honestly I recommend never using on-chain migrations.

@benjamincburns are you the keeper of the current status of this issue? any latest updates on it? thanks!

The situation here has improved dramatically with abi-to-sol v0.8.0 (see [release notes](https://github.com/gnidan/abi-to-sol/releases/tag/v0.8.0)). This tool should now respect existing `internalType` names for existing structs, and if two structs with different names...

@RyanRHall thanks for your feedback! Since your comment, I've made some progress on addressing this limitation. I hope to get some time soon to finish that up!