-
Notifications
You must be signed in to change notification settings - Fork 80
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
2503 doc autogen w/ commit signature #2570
Conversation
…e-cli into 2503-doc-autogen-fresh
added please provide feedback 🙏 there probably needs to be more concrete examples? |
@sukantoraymond please review the sdk documentation |
## Table of Contents | ||
|
||
- [blockchain](#blockchain) | ||
- [constants](#constants) |
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 don't think we need to list every single SDK that we have.
I think we just need to list the main ones:
- Blockchain
- Interchain
- Validator
- Validator Manager
- Interchain
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.
Why don't we want to document the other stuff? I believe we should document everything there is, especially if it's autogenerated. This way the AI we are training on the docs gets more context on all these topics
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.
Approving and merging this PR so that the updated CLI commands go live on the docs site. We should create a new branch to work on the needed updates for the SDK docs ref:#2570 (comment)
Yes, let's get the first version out and then we can iterate on that |
A fresh PR for #2539 as signing commit history and rebasing got annoying