chore: add doc-renderer for generating & updating detailed rule docs #442
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problems:
The new rule document (generated by
npm run new
) was unclear about which part is the header and which part is the body.In
tools/update-docs.ts
, when generating notes and adding them to the header section:header.replace(/\$/g, "$$$$")
join()
it with'\n'
later to create the trailing'\n\n'
This PR:
renderRuleHeader
function and aRuleDocHeader
type to clarify the structure of the header. Then applies this to both the generation and update tools for the detailed rule Markdown files\n\n
between each part of the header in therenderRuleHeader
functionOverview of this PR with image:
This renderer can be used anywhere to produce the header part of the md(x) files
Tested step:
npm run update
and saw no changes, which is my expectation.