LaconicNetwork/cosmos-sdk
7
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 2 Wiki Activity

docs: more app v2 renaming (#21336)

Browse Source
This commit is contained in:
Julien Robert 2024-08-19 09:16:17 +02:00 committed by GitHub
parent cd92990619
commit d6ea8e30b8
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
5 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
UPGRADING.md
View File

@ -727,7 +727,7 @@ When using (legacy) application wiring, the following must be added to `app.go`
app.txConfig = txConfig
```
When using `depinject` / `app v2`, **it's enabled by default** if there's a bank keeper present.
When using `depinject` / `app di`, **it's enabled by default** if there's a bank keeper present.
And in the application client (usually `root.go`):
@ -746,7 +746,7 @@ And in the application client (usually `root.go`):
}
```
When using `depinject` / `app v2`, the tx config should be recreated from the `txConfigOpts` to use `NewGRPCCoinMetadataQueryFn` instead of depending on the bank keeper (that is used in the server).
When using `depinject` / `app di`, the tx config should be recreated from the `txConfigOpts` to use `NewGRPCCoinMetadataQueryFn` instead of depending on the bank keeper (that is used in the server).
To learn more see the [docs](https://docs.cosmos.network/main/learn/advanced/transactions#sign_mode_textual) and the [ADR-050](https://docs.cosmos.network/main/build/architecture/adr-050-sign-mode-textual).

2
client/v2/README.md
View File

@ -38,7 +38,7 @@ Here are the steps to use AutoCLI:
1. Ensure your app's modules implements the `appmodule.AppModule` interface.
2. (optional) Configure how to behave as `autocli` command generation, by implementing the `func (am AppModule) AutoCLIOptions() *autocliv1.ModuleOptions` method on the module.
3. Use the `autocli.AppOptions` struct to specify the modules you defined. If you are using `depinject` / app v2, it can automatically create an instance of `autocli.AppOptions` based on your app's configuration.
3. Use the `autocli.AppOptions` struct to specify the modules you defined. If you are using `depinject`, it can automatically create an instance of `autocli.AppOptions` based on your app's configuration.
4. Use the `EnhanceRootCommand()` method provided by `autocli` to add the CLI commands for the specified modules to your root command.
:::tip

2
docs/build/building-apps/03-app-upgrade.md vendored
View File

@ -53,7 +53,7 @@ be a matter of minutes and not even require them to be awake at that time.
## Integrating With An App
:::tip
The following is not required for users using `depinject` / app v2, this is abstracted for them.
The following is not required for users using `depinject`, this is abstracted for them.
:::
In addition to basic module wiring, setup the upgrade Keeper for the app and then define a `PreBlocker` that calls the upgrade

2
docs/build/building-modules/01-module-manager.md vendored
View File

@ -260,7 +260,7 @@ Here's an example of a concrete integration within an `simapp`:
https://github.com/cosmos/cosmos-sdk/blob/v0.50.0-alpha.0/simapp/app.go#L411-L434
```
This is the same example from `runtime` (the package that powers app v2):
This is the same example from `runtime` (the package that powers app di):
```go reference
https://github.com/cosmos/cosmos-sdk/blob/v0.50.0-alpha.0/runtime/module.go#L61

2
simapp/app_test.go
View File

@ -51,7 +51,7 @@ func TestSimAppExportAndBlockedAddrs(t *testing.T) {
AppOpts: simtestutil.NewAppOptionsWithFlagHome(t.TempDir()),
})
// BlockedAddresses returns a map of addresses in app v1 and a map of modules name in app v2.
// BlockedAddresses returns a map of addresses in app v1 and a map of modules name in app di.
for acc := range BlockedAddresses() {
var addr sdk.AccAddress
if modAddr, err := sdk.AccAddressFromBech32(acc); err == nil {