Danilo Pantani

@Abstrct, thanks for the suggestions. We already have the `--yes` flag. I agree the name could be more intuitive. IMHO, we should only rename and fix the places that are...

@xuht724, we can't reproduce the issue. Is it possible to share the repo code?

great!! thanks for contributing @faddat

> utACK! We should verify it works fine with protos contained in a module too, instead at the root of the app / sdk [this method](https://github.com/ignite/cli/pull/4133/files#diff-c0793c2ae3136f8b122da29528bdc06df36779626e4e50f1c478405a548db0cfR170) gets all proto files...

> How do we provide discovered modules' proto files into code generation process? is almost the same thing as the `protoc`, we are passing the discovered modules to the `include-import`...

> Tried testing off this branch: > > Chain scaffolds ok.. > > On `ignite g ts-client`, I get this prompt: > > ``` > Now ignite supports the `buf.build`...

> still unable to test this properly to check correctness of ts-client output sorry, you are right. The fix is already in the main branch and updated here. But I...

> We may need to throttle or cache BSR requests > > ``` > ✘ Cannot build app: > > error while running command /opt/homebrew/bin/buf generate /Users/clockwork/Documents/Tendermint/venus/proto/venus/venus/query.proto --template=/Users/clockwork/Documents/Tendermint/venus/proto/buf.gen.ts.yaml --output=/Users/clockwork/Documents/Tendermint/venus/ts-client/cosmos.slashing.v1beta1/types --error-format=json...

we should use the same proxy we are using to share the analytics from CLI, for we don't expose the token into the script. Because if we do `curl https://get.ignite.com/cli\!`...

When the script is called, we should make an HTTP request to Google Analytics, passing the version of the Ignite into the request, like the CLI is doing: https://github.com/ignite/cli/blob/9a233e66befb69c1c376d4e3bf662c2ad2e92728/ignite/pkg/gacli/gacli.go#L80-L113 The...