You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: UPGRADING.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -1177,8 +1177,8 @@ The `simapp` package **should not be imported in your own app**. Instead, you sh
1177
1177
#### App Wiring
1178
1178
1179
1179
SimApp's `app_di.go` is using [App Wiring](https://docs.cosmos.network/main/build/building-apps/app-go-di), the dependency injection framework of the Cosmos SDK.
1180
-
This means that modules are injected directly into SimApp thanks to a [configuration file](https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/simapp/app_config.go).
1181
-
The previous behavior, without the dependency injection framework, is still present in [`app.go`](https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/simapp/app.go) and is not going anywhere.
1180
+
This means that modules are injected directly into SimApp thanks to a [configuration file](https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/simapp/app_config.go).
1181
+
The previous behavior, without the dependency injection framework, is still present in [`app.go`](https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/simapp/app.go) and is not going anywhere.
1182
1182
1183
1183
If you are using a `app.go` without dependency injection, add the following lines to your `app.go` in order to provide newer gRPC services:
Copy file name to clipboardexpand all lines: depinject/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -75,7 +75,7 @@ Provider functions serve as the basis for the dependency tree. They are analysed
75
75
76
76
`depinject` supports the use of interface types as inputs to provider functions, which helps decouple dependencies between modules. This approach is particularly useful for managing complex systems with multiple modules, such as the Cosmos SDK, where dependencies need to be flexible and maintainable.
77
77
78
-
For example, `x/bank` expects an [AccountKeeper](https://pkg.go.dev/cosmossdk.io/x/bank/types#AccountKeeper) interface as [input to ProvideModule](https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/x/bank/module.go#L208-L260). `SimApp` uses the implementation in `x/auth`, but the modular design allows for easy changes to the implementation if needed.
78
+
For example, `x/bank` expects an [AccountKeeper](https://pkg.go.dev/cosmossdk.io/x/bank/types#AccountKeeper) interface as [input to ProvideModule](https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/x/bank/module.go#L208-L260). `SimApp` uses the implementation in `x/auth`, but the modular design allows for easy changes to the implementation if needed.
Copy file name to clipboardexpand all lines: depinject/appconfig/README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -201,7 +201,7 @@ satisfy this dependency graph which allows staking and slashing to depend on eac
201
201
In order to test and debug the module configuration, we need to build an app config, generally defined in a YAML file.
202
202
This configuration should be passed first to `appconfig.LoadYAML` to get an `depinject.Config` instance.Then the
203
203
`depinject.Config` can be passed to `depinject.Inject` and we can try to resolve dependencies in the app config.
204
-
Alternatively, the `depinject.Config` can be created via [pure Go code](https://github.com/cosmos/cosmos-sdk/blob/v0.47.0-rc1/simapp/app_config.go).
204
+
Alternatively, the `depinject.Config` can be created via [pure Go code](https://github.com/cosmos/cosmos-sdk/tree/release/v0.50.x/simapp/app_config.go).
In order to facilitate less ad-hoc type checking and assertions and to support flexibility in account balance usage, the existing `x/bank``ViewKeeper` interface is updated to contain the following:
Copy file name to clipboardexpand all lines: x/evidence/README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -219,7 +219,7 @@ The Cosmos SDK handles two types of evidence inside the ABCI `BeginBlock`:
219
219
The evidence module handles these two evidence types the same way. First, the Cosmos SDK converts the CometBFT concrete evidence type to an SDK `Evidence` interface using `Equivocation` as the concrete type.
A new group policy can be created with the `MsgCreateGroupPolicy`, which has an admin address, a group id, a decision policy and some optional metadata.
A new group with policy can be created with the `MsgCreateGroupWithPolicy`, which has an admin address, a list of members, a decision policy, a `group_policy_as_admin` field to optionally set group and group policy admin with group policy address and some optional metadata for group and group policy.
@@ -449,7 +449,7 @@ A new proposal can be created with the `MsgSubmitProposal`, which has a group po
449
449
An optional `Exec` value can be provided to try to execute the proposal immediately after proposal creation. Proposers signatures are considered as yes votes in this case.
A proposal can be withdrawn using `MsgWithdrawProposal` which has an `address` (can be either a proposer or the group policy admin) and a `proposal_id` (which has to be withdrawn).
Copy file name to clipboardexpand all lines: x/group/internal/orm/README.md
+11-11
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ The orm package provides a framework for creating relational database tables wit
21
21
A table can be built given a `codec.ProtoMarshaler` model type, a prefix to access the underlying prefix store used to store table data as well as a `Codec` for marshalling/unmarshalling.
In the prefix store, entities should be stored by an unique identifier called `RowID` which can be based either on an `uint64` auto-increment counter, string or dynamic size bytes.
@@ -42,7 +42,7 @@ The `table` struct is private, so that we only have custom tables built on top o
42
42
`AutoUInt64Table` is a table type with an auto incrementing `uint64` ID.
`PrimaryKeyFields()` method returns the list of key parts for a given object.
@@ -75,25 +75,25 @@ Key parts, except the last part, follow these rules:
75
75
Secondary indexes can be used on `Indexable`[tables](01_table.md). Indeed, those tables implement the `Indexable` interface that provides a set of functions that can be called by indexes to register and interact with the tables, like callback functions that are called on entries creation, update or deletion to create, update or remove corresponding entries in the table secondary indexes.
The currently used implementation of an `indexer`, `Indexer`, relies on an `IndexerFunc` that should be provided when instantiating the index. Based on the source object, this function returns one or multiple index keys as `[]interface{}`. Such secondary index keys should be bytes, string or `uint64` in order to be handled properly by the [key codec](01_table.md#key-codec) which defines specific encoding for those types.
@@ -112,19 +112,19 @@ Both [tables](01_table.md) and [secondary indexes](02_secondary_index.md) suppor
112
112
An `Iterator` allows iteration through a sequence of key value pairs.
Secondary indexes rely on an `indexIterator` that can strip the `RowID` from the full index key in order to get the underlying value in the table prefix store.
Secondary indexes have a `GetPaginated` method that returns an `Iterator` for the given searched secondary index key, starting from the `query.PageRequest` key if provided. It's important to note that this `query.PageRequest` key should be a `RowID` (that could have been returned by a previous paginated request). The returned `Iterator` can then be used with the `Paginate` function and the same `query.PageRequest`.
0 commit comments