id-match bug incorrectly errors on NewExpression

[nickInMN]

Am I misunderstanding what this rule is supposed to do? Version 1.1.0 of ESLint.

I have the following line:
var startDate = new Date();

The rule is configured as:
"id-match": [ 2, "^[a-z$]+([A-Z][a-z]+)*$", { "properties": false } ]

The error I am getting is:
32:25 error Identifier 'Date' does not match the pattern '^[a-z$]+([A-Z][a-z]+)*$' id-match

I thought the idea of this rule is define naming conventions for variables and functions. I get the same error if I try: (yes, I know use [] but was simply a test)
var myArray = new Array();

[eslintbot]

Thanks for the issue! If you're reporting a bug, please be sure to include:

1. The version of ESLint you are using (run eslint -v)
2. What you did (the source code and ESLint configuration)
3. The actual ESLint output complete with numbers
4. What you expected to happen instead

Requesting a new rule? Please see Proposing a New Rule for instructions.

[alberto]

I think your RegExp is wrong. You should remove the first $

[nickInMN]

I want to allow for $ to start a variable name in the case that it is a jQuery variable.

[BYK]

Array and Date are identifiers even if they are predefined globals. Your RegEx's first part only allows lower-case letters, that's why the rule is giving you a warning. Are you suggesting the rule should simply ignore globals?

[nickInMN]

I was under the impression that it would only flag the name of the variable I created, I wasn't expecting to to validate the right hand side.

I suppose ignoring globals would be one way, but even then you may run into this issue if using a third party component. I guess I misunderstood the rule in that I was only expecting it to validate the name of the variable I crated. More specifically, I was expecting it to only validate the left hand side.

[BYK]

@nickInMN - hmm, what you say also makes sense. That's how I constructed my id-length rule. I'd say worth a look.

[BYK]

Okay, looks like this only happens if you use new since NewExpression is different than CallExpression which the code checks against. can you confirm this and this is what you want? If so I'll mark this as accepted.

[nickInMN]

@BYK - Yes, you are correct. If I remove new from that line ESLint behaves as I would expect and there are no errors.

[BYK]

@nickInMN - Alright, I'm gonna update the title of your issue then and try to submit a patch soon :)