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

Provide meta prerequisites for automatic document generation #184

Closed
4 tasks done
MikeMcC399 opened this issue Apr 23, 2024 · 1 comment
Closed
4 tasks done

Provide meta prerequisites for automatic document generation #184

MikeMcC399 opened this issue Apr 23, 2024 · 1 comment
Assignees

Comments

@MikeMcC399
Copy link
Collaborator

MikeMcC399 commented Apr 23, 2024

This is a suggestion to provide or modify the necessary meta tags to enable automatic documentation generation using eslint-doc-generator.

ESLint doc generator recommendations

The ESLint organization recommends using the npm module eslint-doc-generator (Automatic documentation generator for ESLint plugins and rules) to support the generation of consistent documentation for ESLint plugins.

In its Configure Linting documentation it recommends the following:

... enable the recommended rules from eslint-plugin-eslint-plugin as well as:

Current compatibility

The repo is currently not compatible with the recommendations. The items in the following list can be checked off as they are addressed

Pass rules from:

The eslint-plugin/recommended rules fail due to meta.type and meta.schema. The rules eslint-plugin/require-meta-docs-description and eslint-plugin/require-meta-docs-url fail individually.

@MikeMcC399
Copy link
Collaborator Author

The set of 9 rules in this repo have now all been adjusted so that their meta properties pass linting for use with the eslint-doc-generator (Automatic documentation generator for ESLint plugins and rules).

The next step will be to apply the doc generator to the repo.

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

No branches or pull requests

1 participant