You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is that all markdown files for each individual lint rule is present in the cli repo, and docs.deno.com renders them out, in a similar fashion to lint.deno.land. This gives much better visibility for rules, while also giving us the possibility to have more structured pages for lint rules.
Things needed to be done to do this in the deno repository:
Add a directory for markdown files for all rules, however does not include these in the binary
Add a subcommand/flag to get a list of all the lint rules without any additional information
Add a lint step in the CI that checks any added rules have a corresponding markdown file
Things to do in this repository:
Add a sparse submodule to the deno repository
Update the release step to automatically bump the submodule
Move over rendering of relevant components from https://github.com/denoland/deno_lint/tree/main/www. Depending on the approach decided structure, either create a new .page.tsx, or modify the _includes/doc.tsx to special-case the lint command to render additional information
The text was updated successfully, but these errors were encountered:
This is a solution for denoland/deno_lint#1300.
The idea is that all markdown files for each individual lint rule is present in the cli repo, and docs.deno.com renders them out, in a similar fashion to lint.deno.land. This gives much better visibility for rules, while also giving us the possibility to have more structured pages for lint rules.
Things needed to be done to do this in the deno repository:
Things to do in this repository:
.page.tsx
, or modify the_includes/doc.tsx
to special-case thelint
command to render additional informationThe text was updated successfully, but these errors were encountered: