Add ??? flag to variable-name rule

[unional]

Bug Report

• TSLint version: 3.10.2
• TypeScript version: 1.9.0-dev.20160614-1.0
• Running TSLint via: VSCode

TypeScript code being linted

export interface Foo {

}

// [tslint] variable name must be in camelcase or uppercase
export const Foo = { 
  someFunction() {}
}

Is there a better construct without hitting this warning or getting into class + static method?
how can I disable this rule only for this use case (maybe adding a bypass-overload flag)?

[jkillian]

You could add the allow-pascal-case option to allow this format of name in general.

[unional]

Yes, but that's what I don't want to.
This is really a type + utility construct. And being a type it should be uppercase.
The utility part is really a namespace idea, not a variable.

[wovalle]

I'm facing this issue, I don't want to allow all my variables to be pascal-case but the exported ones (mostly react functional components).

[ajafff]

@wovalle
I'd like to suggest one of my custom rules: https://github.com/ajafff/tslint-consistent-codestyle/blob/master/docs/naming-convention.md#examples

Example config for your use case:

"naming-convention": [
    true,
    {"type": "variable", "format": "camelCase"},
    {"type": "variable", "modifiers": "export", "format": "PascalCase", "final": true}
]

[JoshuaKGoldberg]

Duplicate of #522