Starport type is too verbose

I tried running through a tutorial of using starport and saw “starport type” created 12 new files and modified another 9 files. That was too many files just to create ONE data model.

Normal app often have a few dozens to a hundred data models. Imagine how many files does it create? Go is supposed to be a succinct language but this is even worse than Java.

Does anyone actually use “starport type” to generate all the models in your app? Is there any better way to make it less verbose?

1 Like

starport type scaffolds not only a type, but a whole set of CRUD operations with messages, proto files, handlers, CLI commands etc. This may seem like a lot of files (and it is), but type is very useful for providing a better understanding of the whole lifecycle of a transaction. We also have a message command that scaffolds a single message and in the next version of Starport we’ll also have a query command for more fine-grained scaffold.

The overall point, however, is very much valid: Cosmos SDK is indeed a bit too verbose and requires a lot of boilerplate code.

Also, we’re not actively monitoring this forum, so with any questions and suggestions, please, visit the Starport channel on https://discord.gg/vcExX9T

If you noticed a bug or something’s not working as expected, please, create an issue on GitHub - tendermint/starport: The easiest way to build a blockchain.

2 Likes