We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
i think that the readme should be generated automatically by a script, so that bugs like #1263 will never happen again.
in my own eslint plugin, i use a custom script to accomplish this: https://github.com/IsaacScript/isaacscript/blob/main/packages/eslint-plugin-isaacscript/scripts/generateReadme.mts
so I think you could do something similar with this plugin.
The text was updated successfully, but these errors were encountered:
Yeah, would be good to add it to our generateRule script, thanks.
generateRule
Sorry, something went wrong.
How about onboarding to eslint-doc-generator? It's pretty commonly used in the ecosystem, and quite handy.
eslint-doc-generator
No branches or pull requests
i think that the readme should be generated automatically by a script, so that bugs like #1263 will never happen again.
in my own eslint plugin, i use a custom script to accomplish this: https://github.com/IsaacScript/isaacscript/blob/main/packages/eslint-plugin-isaacscript/scripts/generateReadme.mts
so I think you could do something similar with this plugin.
The text was updated successfully, but these errors were encountered: