id-match
Require identifiers to match a specified regular expression
This rule is currently frozen and is not accepting changes.
“There are only two hard things in Computer Science: cache invalidation and naming things.” — Phil Karlton
Naming things consistently in a project is an often underestimated aspect of code creation.
When done correctly, it can save your team hours of unnecessary head scratching and misdirections.
This rule allows you to precisely define and enforce the variables and function names on your team should use.
No more limiting yourself to camelCase, snake_case, PascalCase, or HungarianNotation. id-match
has all your needs covered!
Rule Details
This rule requires identifiers in assignments and function
definitions to match a specified regular expression.
Options
This rule has a string option for the specified regular expression.
For example, to enforce a camelcase naming convention:
{
"id-match": ["error", "^[a-z]+([A-Z][a-z]+)*$"]
}
Examples of incorrect code for this rule with the "^[a-z]+([A-Z][a-z]+)*$"
option:
/*eslint id-match: ["error", "^[a-z]+([A-Z][a-z]+)*$"]*/
var = "#112C85";
var = "#112C85";
var = "#112C85";
var = "#112C85";
function () {
// ...
}
class {}
class myClass {
() {}
}
class anotherClass {
() {}
}
Examples of correct code for this rule with the "^[a-z]+([A-Z][a-z]+)*$"
option:
/*eslint id-match: ["error", "^[a-z]+([A-Z][a-z]+)*$"]*/
var myFavoriteColor = "#112C85";
var foo = bar.baz_boom;
var foo = { qux: bar.baz_boom };
do_something();
var obj = {
my_pref: 1
};
class myClass {}
class anotherClass {
doSomething() {}
}
class oneMoreClass {
#doSomething() {}
}
This rule has an object option:
"properties": false
(default) does not check object properties"properties": true
requires object literal properties and member expression assignment properties to match the specified regular expression"classFields": false
(default) does not check class field names"classFields": true
requires class field names to match the specified regular expression"onlyDeclarations": false
(default) requires all variable names to match the specified regular expression"onlyDeclarations": true
requires onlyvar
,const
,let
,function
, andclass
declarations to match the specified regular expression"ignoreDestructuring": false
(default) enforcesid-match
for destructured identifiers"ignoreDestructuring": true
does not check destructured identifiers
properties
Examples of incorrect code for this rule with the "^[a-z]+([A-Z][a-z]+)*$", { "properties": true }
options:
/*eslint id-match: ["error", "^[a-z]+([A-Z][a-z]+)*$", { "properties": true }]*/
var obj = {
: 1
};
obj. = function() {
// ...
};
classFields
Examples of incorrect code for this rule with the "^[a-z]+([A-Z][a-z]+)*$", { "classFields": true }
options:
/*eslint id-match: ["error", "^[a-z]+([A-Z][a-z]+)*$", { "classFields": true }]*/
class myClass {
= 1;
}
class anotherClass {
= 1;
}
onlyDeclarations
Examples of correct code for this rule with the "^[a-z]+([A-Z][a-z]+)*$", { "onlyDeclarations": true }
options:
/*eslint id-match: [2, "^[a-z]+([A-Z][a-z]+)*$", { "onlyDeclarations": true }]*/
foo = __dirname;
ignoreDestructuring: false
Examples of incorrect code for this rule with the default "^[^_]+$", { "ignoreDestructuring": false }
option:
/*eslint id-match: [2, "^[^_]+$", { "ignoreDestructuring": false }]*/
var { } = query;
var { = 1 } = query;
var { : } = query;
var { category_id: } = query;
var { category_id: categoryId, ... } = query;
ignoreDestructuring: true
Examples of incorrect code for this rule with the "^[^_]+$", { "ignoreDestructuring": true }
option:
/*eslint id-match: [2, "^[^_]+$", { "ignoreDestructuring": true }]*/
var { category_id: } = query;
var { category_id, ... } = query;
Examples of correct code for this rule with the "^[^_]+$", { "ignoreDestructuring": true }
option:
/*eslint id-match: [2, "^[^_]+$", { "ignoreDestructuring": true }]*/
var { category_id } = query;
var { category_id = 1 } = query;
var { category_id: category_id } = query;
When Not To Use It
If you don’t want to enforce any particular naming convention for all identifiers, or your naming convention is too complex to be enforced by configuring this rule, then you should not enable this rule.
Version
This rule was introduced in ESLint v1.0.0.