README.md
is a generated file. Do not edit it directly. Edit the files inside .README
instead.
When making a commit, the following Pre-Commit hooks run:
- tests
- lint
- commit message validation (see "Commit Messages" below)
All commit messages must begin with one of the following prefixes:
fix:
feat:
refactor:
docs:
chore:
The prefix is used to bump the correct segment of the version number automatically during deploy.
Run them with npm t
.
Run with npm run lint
.
- Create a file in
tests/rules/assertions
named thecamelCase
version of your rule name with the following template:
export default { invalid: [], valid: [] }
- Add your test file to
tests/rules/index.js
- Create a file in
src/rules
named thecamelCase
version of your rule name - Add your rule file to
src/index.js
- Create new file in
./.README/rules/[rule-name].md
.
- Use ./.README/rules/require-valid-file-annotation.md as a template.
- Ensure that rule documentation document includes
<!-- assertions spaceAfterTypeColon -->
declaration.
- Update ./.README/README.md to include the new rule.
A CI service will build and publish the new documentation.
Note: The section "The following patterns are considered problems:" and "The following patterns are not considered problems:" is generated automatically using the test cases.