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.
I realized
Uncategorized
section is duplicate: README.md.npm run update
seems wrong, but it's difficult to identify the cause.This PR rewrites the
npm run update
script to be readable.tools/lib/rules.js
provides the rule list to be used by update scripts.tools/lib/categories.js
provides the category list to be used by update scripts.tools/update-docs.js
updates the header ofdocs/rules/*.md
files.tools/update-lib-configs.js
updateslib/configs/*.js
files.tools/update-lib-index.js
updateslib/index.js
file.tools/update-readme.js
updates the rule tables oflib/README.md
file.Additionally, this PR changes this internal structure a bit.
lib/*-rules.js
files andnpm run update
updateslib/configs/*.js
directly. Because we don't havelib/config/use-with-caution.js
before, but the script seems to makelib/use-with-caution-rules.js
if rules exist. This can cause mistakes in future.npm run update
updateslib/index.js
instead of usingrequire-all
at runtime.)It will make easy to use this plugin in browsers.
And this PR changes documents a bit:
docs/rules/*.md
files to show which config includes each rule.vue/
prefix to rule IDs in the doc.