A custom tslint rule to ban configurable lists of code snippets.
npm install tslint-ban-snippetsA custom tslint rule to ban configurable lists of code snippets.
examples: "return void reject", "it.only", "debugger".
tslint-ban-snippets is stable and in use every day in CI builds and on dev boxes (Linux, Mac, Windows) for at least one major product.
tslint-ban-snippets WILL be maintained, as long as tslint is around. BUT recommend switching to the eslint equivalent, eslint-plugin-ts-ban-snippets.
No special dependencies - just TypeScript and of course tslint.
- a custom tslint rule that can detect code snippets that are not desired
- configurable for multiple code snippets
- can include/exclude file paths
- the error message can also be configured
The rule is quite flexible and could potentially avoid having to create multiple custom tslint rules.
The custom rule tsl-ban-snippets can be configured with small snippets of code that should NOT be used by developers.
If tslint finds the snippets of code, it will raise an error for that line of code.
In this way, a code base can be kept clean of unwanted coding practices.
The rule name is tsl-ban-snippets to avoid using the prefix tslint- which was found to be problematic when other tslint libraries are in use.
There is a standard tslint rule named ban. However its scope is quite limited - the tsl-ban-snippets rule applies to any statement in a TypeScript file, and so can be configured to detect most unwanted code snippets.
``
npm install tslint-ban-snippets
Edit your tslint.json to have an entry "rulesDirectory" that points to tslint-ban-snippets.
Normally this would be like:
`json`
{
"rulesDirectory": "node_modules/tslint-ban-snippets/dist/lib",
"rules": {
"tsl-ban-snippets": [
// custom banned snippets here...
]
}
}
Alternatively, you can store the custom rules in a separate file:
tslint.json:
`json
{
"extends": ["./tslint.tslint-ban-snippets.json"],
// ...
}
tslint.tslint-ban-snippets.json:
`json`
{
"rulesDirectory": "node_modules/tslint-ban-snippets/dist/lib",
"rules": {
"tsl-ban-snippets": [
// custom banned snippets here...
]
}
}
Now you can configure the custom rule, to ban whatever code snippets you do NOT want developers to use.
#### examples
Example of how to ban the use of "return void":
`json`
"rules": {
// other rules here...
"tsl-ban-snippets": [
true,
{
"banned": [
{
"snippets": ["return void"]
}
]
}
]
}
Example to ban the disabling of tests:
`json`
"rules": {
"tsl-ban-snippets": [
true,
{
"banned": [
{
"snippets": ["it.only", "describe.only"],
"message": "Do not enable only some tests."
},
{
"snippets": ["it.skip", "describe.skip"],
"message": "Do not skip tests."
}
]
}
]
}
Example that uses a regular expression, to ban both return void reject and return void resolve:
`json`
"rules": {
// other rules here...
"tsl-ban-snippets": [
true,
{
"banned": [
{
"regexSnippets": ["return void [reject|resolve]"],
}
]
}
]
}
Here is another example, with more options.
This example bans return void aswell as return void reject and return void resolve.
`json``
"rules": {
// other rules here...
"tsl-ban-snippets": [
true,
{
"banned": [
{
"snippets": ["return void"],
"message": "Please do not return void - instead place the return statement on the following line.",
"includePaths": [".ts", ".tsx"],
"excludePaths": ["itest"]
},
{
"regexSnippets": ["return void [reject|resolve]"],
"message": "Please do not return void - instead place the return statement on the following line.",
"includePaths": [".ts", ".tsx"],
"excludePaths": []
}
]
}
]
}
For more examples of how to configure, please see tslint.json.
For working tests, please see the unit tests.
For a real code example, see the test harness and in particular the config file.
| site | URL |
| -------------------- | ------------------------------------------------- |
| source code (github) | https://github.com/mrseanryan/tslint-ban-snippets |
| github page | https://mrseanryan.github.io/tslint-ban-snippets/ |
| npm | https://www.npmjs.com/package/tslint-ban-snippets |
see the contributing readme.
This project is based on the excellent seeder project typescript-library-starter.
The project was started to avoid having to repeatedly fix similar coding issues in large TypeScript code bases.
Original work by Sean Ryan - mr.sean.ryan(at gmail.com)
This project is licensed under the MIT License - see the LICENSE file for details