Skip to content
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: generate chain config documentation automatically #4113

Merged
merged 15 commits into from
May 16, 2024
Merged

Conversation

Pantani
Copy link
Collaborator

@Pantani Pantani commented Apr 29, 2024

Description

Generate chain config documentation automatically.

Now the config struct has the tag field doc, so we can add a description and automatically generate the documentation related to the chain configuration file.

@Pantani Pantani self-assigned this Apr 29, 2024
@Pantani Pantani changed the title feat: Generate chain config documentation automatically feat: generate chain config documentation automatically Apr 29, 2024
ignite/config/chain/base/config.go Show resolved Hide resolved
ignite/config/chain/base/config.go Outdated Show resolved Hide resolved
ignite/internal/tools/gen-config-doc/cmd/root.go Outdated Show resolved Hide resolved
@Pantani Pantani requested a review from julienrbrt May 3, 2024 13:41
julienrbrt
julienrbrt previously approved these changes May 8, 2024
@Pantani Pantani enabled auto-merge (squash) May 15, 2024 09:23
julienrbrt
julienrbrt previously approved these changes May 15, 2024
@Pantani Pantani merged commit 239d92f into main May 16, 2024
46 checks passed
@Pantani Pantani deleted the feat/config-docs branch May 16, 2024 14:49
julienrbrt pushed a commit that referenced this pull request May 29, 2024
* add pkg to read doc struct tag and add config doc tags

* create a tool to generate config files documentation

* add changelog

* use the ouput as a yaml

* fix tests and lint

---------

Co-authored-by: Pantani <Pantani>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants