-
Notifications
You must be signed in to change notification settings - Fork 552
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: scaffold chain-registry files #4413
Conversation
Use: "chain-registry", | ||
Short: "Configs for the chain registry", | ||
Long: `Scaffold the chain registry chain.json and assets.json files. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should certain fields should be configurable?
For instance:
c.Flags().String("status", "upcoming", "Chain status (mainnet, testnet, upcoming, etc.)")
and then consumed in scaffoldChainRegistryFiles
status, _ := cmd.Flags().GetString("status")
And passed down to AddChainRegistryFiles
if err = sc.AddChainRegistryFiles(c, cfg, status); err != nil {
return err
}
``
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't super sure. As youd scaffold this when you need the frontend, and usually it is at devnet. Wanted to keep it KISS. But we can always add if you find it valuable.
* feat: scaffold chain-registry files * cl * cl * updates * updates * typo * renaming * finalize chain-registry * updates * lint * lint * typos (cherry picked from commit ed3d0b3)
Create a new command for scaffold chain-registry template files.
ignite s chain-registry
It will be useful for this: ignite/apps#140, in order to have the js wallet connect be able to easily add the chain.
Additionally, it is useful when a chain gets to testnet and launching phase, to have those files ready to publish on https://github.com/cosmos/chain-registry