Open toschdev opened 9 months ago
Thank you.
checkers-app
and the module checkers
to offer a clearer distinction to the learner. Any advice as to the naming convention and the -
character?About the content's other parts:
EndBlock
or whatever replaces it in ABCI++?Hello Xavier,
-
char is fine to use. I'd recommend then scaffold the chain first without module, then add the checkers
module:ignite scaffold chain checkers-app --no-module && cd checkers-app
ignite scaffold module checkers
About the content's other part
store.KVStoreService
, in line with SDK v0.50I am adding ideas to handle in the upgraded content.
--address-prefix checkers
when scaffolding the chain. Unless you think of a better prefix.ignite chain serve
without custom module. Relevant actions to look around what is available?app_config.go
as opposed to app.yaml
?Initial suggestions and questions to Ignite:
generate ts-client
, force all npm versions without ^
.cosmjs-types
?ts-client
, have an initially populated .env
.ts-client
, there are a lot of duplicates, for instance pagination.ts
. ts-client
, perhaps the folders like cosmos.auth.v1beta1
could be kept inside a generated
folder to clean up the look.ts-client
modifies the generated files so much as to make it difficult to know what really changed the second time it was run. This is visible when you use Git for the diff.scaffold react
is not ready? I get Failed to resolve import "../hooks/useClient" from "src/def-hooks/useAddress.ts"
react
folder as a git submodule, I cannot scaffold a module: Open .../tmp-checkers-app/react/.git: is a directory
.checkers
module, I cannot really make it a submodule because the proto folder is not with it but instead is in the checkers-app
. It would have been nice for it to be self-contained. Same remark about the api
folder. Compare this to chain-minimal.nil
. For instance.GetAllStoredGame
. What I did by hand.
Step-by-Step Upgrade Guide
There should be no major issue following the tutorial with v28.0.0 of Ignite, using Cosmos SDK v0.50.1
with
Docker Version upgrades Upgrade the Ignite version for the docker container accordingly.
Change in Module Path The path for
module.go
has changed to:x/checkers/module/module.go
Frontend Scaffolding Options Frontend Scaffolding is no longer default to Vue. Now, you can choose between Vue, React, Go or TypeScript
Use these commands:
Update Scaffold Message for CreatePost Command Make sure to update the output for the scaffolded
createPost
commandAutoCLI Path Change The file
x/checkers/client/cli/tx_create_post.go
is now integrated with AutoCLI atx/checkers/module/autocli.go
Adjustment in Stored Game Update the store
stored_game.go
as follows:Not sure if The "Adjustment" in chapter Store Object is necessary.
Chain-ID Requirements in CLI tx commands CLI transaction commands require a chain-id flag now. For example:
Potential Issues and Resolutions
Dependency Conflicts: Ensure all dependencies are compatible with v28.0.0. Conflicts may arise due to the upgrade. Docker Image Compatibility: Verify that the Docker image version aligns with the CLI version to avoid compatibility issues. Frontend Scaffolding: If using a frontend framework, ensure it's correctly scaffolded as per the new commands. Old projects may need manual adjustments. AutoCLI Integration: Check for any discrepancies caused by the new AutoCLI integration path and adjust your code accordingly.
Would appreciate your feedback on the upgrade
For more insights, it's valuable to check how tutorials have been upgraded within Ignite docs. Checkout the amazing PR by @jeronimoalbi https://github.com/ignite/cli/pull/3705/files