Denis Fadeev

Not being able to mount commands in places like `ignite chain` and `ignite scaffold` means there are limits to how plugins can really "extend" CLI from users' point of view....

Is it possible to enforce flags to be submitted after the command? ``` ❌ ignite scaffold --path ./xxx/yyy wasm ``` ``` ✅ ignite scaffold wasm --path ./xxx/yyy ```

But arguments will follow the command, right? You can't have `ignite scaffold arg1 arg2 foo`, it's always `ignite scaffold foo arg1 arg2`.

Reopening this. I think this is a very useful feature to have.

The minimum amount is 1M. We should print a warning when a user supplied less than that and default to sensible values when it's a testnet.

> We shouldn't use private repo to launch on the chain itself I think there are valid use-cases for launching from private repos.

@aljo242 we might want to reopen this one as well.

Same goes for scaffolding queries: ``` ignite s type comment body ignite s query show-blog id --response comments:Comment ``` ```proto // Currently: message QueryShowBlogResponse { Comment comments = 1; }...

@aljo242 I propose we bump the priority of this issue. It should be reasonably straightforward to fix, and will significantly improve the scaffolding experience.

This, and also a coordinator may set values in `config.yml` that will be automatically applied to `app.toml` and `config.toml`. Most likely a different issue.