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

Automate docs with eslint-doc-generator #117

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bmish
Copy link
Contributor

@bmish bmish commented Oct 30, 2022

I built this CLI tool eslint-doc-generator for automating the generation of the README rules list table and rule doc title/notices for ESLint plugins. It follows common documentation conventions from this and other top ESLint plugins and will help us standardize documentation across ESLint plugins (and generally improve the usability of custom rules through better documentation and streamline the process of adding new rules). It has 100% test coverage and is already used in many popular ESLint plugins.

"eslint-import-resolver-typescript": "^2.5.0",
"eslint-plugin-import": "^2.25.3",
"eslint-plugin-jest": "^25.2.4",
"eslint-plugin-jest-formatting": "file:.",
"eslint-plugin-prettier": "^4.0.0",
"jest": "^27.3.1",
"prettier": "2.4.1",
"typescript": "^4.4.4",
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like an autoformattin and I'm ok with it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The dependencies were automatically sorted when I ran npm i --save-dev eslint-doc-generator.

@dangreenisrael
Copy link
Owner

If you want to do a cleanup to remove old rules, could you do that in a separate PR?

@dangreenisrael
Copy link
Owner

dangreenisrael commented Nov 7, 2022

Also, if you felt like upgrading the base image in a separate PR that would be more than welcome as well 😄

@bmish bmish force-pushed the eslint-doc-generator branch 6 times, most recently from 92b3df7 to 4ee2911 Compare November 9, 2022 17:38
@bmish
Copy link
Contributor Author

bmish commented Nov 9, 2022

@dangreenisrael

If you want to do a cleanup to remove old rules, could you do that in a separate PR?

Removing docs for deleted rules in #118.

Also, if you felt like upgrading the base image in a separate PR that would be more than welcome as well 😄

What do you mean exactly?

Regarding CI, eslint-doc-generator requires Node >= 14, causing CI to fail when installing deps and running linting on Node 12. I split out the lint job to only run under Node 18 and switched to yarn install --ignore-engines to install dependencies.

@bmish bmish force-pushed the eslint-doc-generator branch 2 times, most recently from 7bc1c8d to e0b2bb5 Compare November 17, 2022 19:09
@bmish bmish force-pushed the eslint-doc-generator branch 2 times, most recently from 13f7229 to 47f6184 Compare December 2, 2022 16:35
@bmish
Copy link
Contributor Author

bmish commented Dec 2, 2022

Can someone approve CI to run? This is still ready to go in. @dangreenisrael @twelve17 @hockeybuggy

@benkimpel
Copy link
Collaborator

@bmish I've approved the CI run, however, I'd like to leave it up to @dangreenisrael to do the merge on this one since this PR could impact how he manages this repo (generating the docs, for example.)

@benkimpel
Copy link
Collaborator

@bmish I also rebased this onto latest after merging your other PR.

@dangreenisrael
Copy link
Owner

Are we still looking to land this?

@bmish
Copy link
Contributor Author

bmish commented Jun 19, 2023

@dangreenisrael yes still ready to go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants