Merge PR #4403: Paramchange proposal skips omitempty fields
This commit is contained in:
committed by
Alexander Bezobchuk
parent
8fecc7724b
commit
91e75cb74a
@@ -26,7 +26,8 @@ func GetCmdSubmitProposal(cdc *codec.Codec) *cobra.Command {
|
||||
Short: "Submit a parameter change proposal",
|
||||
Long: strings.TrimSpace(
|
||||
fmt.Sprintf(`Submit a parameter proposal along with an initial deposit.
|
||||
The proposal details must be supplied via a JSON file.
|
||||
The proposal details must be supplied via a JSON file. For values that contains
|
||||
objects, only non-empty fields will be updated.
|
||||
|
||||
IMPORTANT: Currently parameter changes are evaluated but not validated, so it is
|
||||
very important that any "value" change is valid (ie. correct type and within bounds)
|
||||
@@ -34,7 +35,7 @@ for its respective parameter, eg. "MaxValidators" should be an integer and not a
|
||||
|
||||
Proper vetting of a parameter change proposal should prevent this from happening
|
||||
(no deposits should occur during the governance process), but it should be noted
|
||||
regardless.
|
||||
regardless.
|
||||
|
||||
Example:
|
||||
$ %s tx gov submit-proposal param-change <path/to/proposal.json> --from=<key_or_address>
|
||||
|
||||
Reference in New Issue
Block a user