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
I am currently upgrading a project from Cosmos SDK v0.47 to v0.50.3. In the previous version, we used the GetMinter() function from the x/mint module to access the Inflation property for our custom module.
However, with the release of v0.50, it appears that GetMinter() has been removed as part of a broader migration to collection (as detailed in the upgrading guide).
Could you provide guidance or examples on how to properly access the Minter state using the collections framework in Cosmos SDK v0.50.3? Any advice on transitioning from the direct usage of GetMinter() to the new recommended approach would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
@julienrbrt Thanks.
Is it possible to access Minter from another module?
I thought it needs to define interface at expected_keepers.go to access keeper from the module.
Right, so you cannot use the struct field in an interface indeed. That's indeed a drawback but this let module expose only what they want.
There was discussion about putting all collections fields private as well.
If you need to query mint you can use its query server.
I am currently upgrading a project from Cosmos SDK v0.47 to v0.50.3. In the previous version, we used the GetMinter() function from the
x/mint
module to access the Inflation property for our custom module.However, with the release of v0.50, it appears that GetMinter() has been removed as part of a broader migration to collection (as detailed in the upgrading guide).
Could you provide guidance or examples on how to properly access the Minter state using the collections framework in Cosmos SDK v0.50.3? Any advice on transitioning from the direct usage of GetMinter() to the new recommended approach would be greatly appreciated.
The text was updated successfully, but these errors were encountered: