-
Notifications
You must be signed in to change notification settings - Fork 34
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
Create table of rules in README generated from metadata #36
Comments
anderseknert
added a commit
that referenced
this issue
Apr 12, 2023
And generate a table for our README :) NOTE: This should be integrated in the build, so that whenever a built-in is added or updated, a new table is generated. I plan to look into build-related improvements later, so doing this manually for now. Fixes #36 Signed-off-by: Anders Eknert <anders@styra.com>
anderseknert
added a commit
that referenced
this issue
Apr 12, 2023
And generate a table for our README :) NOTE: This should be integrated in the build, so that whenever a built-in is added or updated, a new table is generated. I plan to look into build-related improvements later, so doing this manually for now. Fixes #36 Signed-off-by: Anders Eknert <anders@styra.com>
anderseknert
added a commit
that referenced
this issue
Apr 12, 2023
And generate a table for our README :) NOTE: This should be integrated in the build, so that whenever a built-in is added or updated, a new table is generated. I plan to look into build-related improvements later, so doing this manually for now. Additionally, configure `gci` linter to group imports. Fixes #36 Signed-off-by: Anders Eknert <anders@styra.com>
anderseknert
added a commit
that referenced
this issue
Apr 12, 2023
And generate a table for our README :) NOTE: This should be integrated in the build, so that whenever a built-in is added or updated, a new table is generated. I plan to look into build-related improvements later, so doing this manually for now. Additionally, configure `gci` linter to group imports. Fixes #36 Signed-off-by: Anders Eknert <anders@styra.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While we could do this by hand, this is likely to get out of sync with the real world quickly. It should be fairly "easy" to create a Go utility, that scans metadata of all rules in the
bundle
directory and creates a markdown table for display. This table should include:The rule name should be a link pointing to the Styra docs for the rule.
The text was updated successfully, but these errors were encountered: