UPDATE: Respect the minimum-gas-prices configuration

[Olshansk]

In one of our PRs, we need to manually match up code with config.yml because some defaults are not copied over by ignite (see the following screenshot).

This is a request to reflect minimum-gas-prices when running ignite generate

[okdas]

I believe this is not a bug but is done intentionally for some reason.

I've noticed that after one of the ignite updates, the content of app.toml no longer carries over the comments for configuration options as well. I'd love to know the reasoning behind this decision. :)

[Pantani]

@Olshansk ignites replies to all the configurations from the ignite config.yaml for your app config when you init your chain using the ignite chain init or ignite chain serve. After this PR, we also replied to the config using the chain build, debug, and faucet commands.

You can see here, first, we set a default value for minimum-gas-prices, and after, we replace it with the value if the user defines the value into the ignite config yaml

cli/ignite/services/chain/runtime.go

Lines 119 to 129 in ffc8e64

	staked, err := sdktypes.ParseCoinNormalized(validator.Bonded)
	if err != nil {
	return err
	}
	gas := sdktypes.NewInt64Coin(staked.Denom, 0)
	appConfig.Set("minimum-gas-prices", gas.String())
	// Update config values with the validator's Cosmos SDK app config
	if err := updateTomlTreeValues(appConfig, validator.App); err != nil {
	return err
	}

[Pantani]

@okdas, The reason is that the go YAML parser can't parse the comments correctly, and the comments are tough to maintain if we edit the file from the code

[Pantani]

@Olshansk, the ignite generate command is agnostic to the config file. It doesn't need a config file, and replacing config files using a command unrelated to the init chain can be a mess for some users