Method names should support symbol properties

[slikts]

The current function-name rule fails when implementing an iterable:

const it: Iterable<any> = {
  // [tslint] Method name does not match /^[a-z][\w\d]+$/: [Symbol.iterator] (function-name)
  [Symbol.iterator](): any {}
}

It should not fail; symbol properties and the iterable protocol are standard parts of JS since many years ago and should be supported.

[JoshuaKGoldberg]

Hi slikts 👋 thanks for the issue! You're absolutely right, this is a bug and should be fixed.

[elado]

here's my override:

"function-name": [true, {
  "method-regex": "^\\*?\\[?[a-zA-Z][\\w\\d\\.]*\\]?$",
  "private-method-regex": "^\\*?\\[?[a-zA-Z][\\w\\d\\.]*\\]?$",
  "protected-method-regex": "^\\*?\\[?[a-zA-Z][\\w\\d\\.]*\\]?$",
  "static-method-regex": "^\\*?\\[?[a-zA-Z][\\w\\d\\.]*\\]?$",
  "function-regex": "^\\*?\\[?[a-zA-Z][\\w\\d\\.]*\\]?$"
}],

(and it also allows lowercase static methods, so it's a bit different than the original)

[joelalejandro]

@JoshuaKGoldberg Is there a scheduled date for the 5.2.2 version of the package to include this fix? We're using this set of rules via tslint-config-airbnb and we're finding the same issue. We're applying a local override in the meantime, but it would be nice to see this go live :)

[JoshuaKGoldberg]

Thanks for bringing his up @joelalejandro - I'm planning on releasing a version after Hacktoberfest ends / early first week of November. It wasn't mentioned at all so I'll file a separate issue.