feat: deprecate x/params usage in x/bank (#12630)
This commit is contained in:
@@ -71,7 +71,7 @@ Migration functions should live inside the `migrations/` folder of each module,
|
||||
```go
|
||||
// Migrate1to2 migrates from version 1 to 2.
|
||||
func (m Migrator) Migrate1to2(ctx sdk.Context) error {
|
||||
return v043bank.MigrateStore(ctx, m.keeper.storeKey) // v043bank is package `x/bank/migrations/v043`.
|
||||
return v2bank.MigrateStore(ctx, m.keeper.storeKey) // v043bank is package `x/bank/migrations/v2`.
|
||||
}
|
||||
```
|
||||
|
||||
|
||||
@@ -135,7 +135,7 @@ message QueryParamsResponse {
|
||||
As a result of implementing the module parameter methodology, we gain the ability
|
||||
for module parameter changes to be stateful and extensible to fit nearly every
|
||||
application's use case. We will be able to emit events (and trigger hooks registered
|
||||
to that events using the work proposed in [even hooks](https://github.com/cosmos/cosmos-sdk/discussions/9656)),
|
||||
to that events using the work proposed in [event hooks](https://github.com/cosmos/cosmos-sdk/discussions/9656)),
|
||||
call other Msg service methods or perform migration.
|
||||
In addition, there will be significant gains in performance when it comes to reading
|
||||
and writing parameters from and to state, especially if a specific set of parameters
|
||||
|
||||
Reference in New Issue
Block a user