CamelCase option to allow snake_case in object literals

There are situations where third-party code or services are configured by calling a function with an object literal. Those objects are flagged the camelCase rule:

var snakes = require('somesnakelib');  // not my code
snakes({snake_prop: true});  // ESLint: "Identifier 'snake_prop' is not in camel case."

JSCS dealt with this by adding an ignoreProperties option to their CamelCase rule. I like enforcing names and would rather not disable the CamelCase rule to use code that I don’t control without errors.

This was touched on in #656, #672, #674 and #1550, but object literals are still being flagged.

<bountysource-plugin>

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource. </bountysource-plugin>

[OmgImAlexis]

@nzakas any reason a commit was merged but without the “nonmethods” option?

[OmgImAlexis]

@nzakas any updates on this?

I have the code below yet I’m still getting an error.

var client = tumblr.createClient({
    'consumer_key': config.get('tumblr:token'),
    'consumer_secret': config.get('tumblr:tokenSecret'),
    'token': tokenSet.token,
    'token_secret': tokenSet.tokenSecret
});

I’m using @sindresorhus’s xo linter.

    "xo": {
        "space": 4,
        "rules": {
            "space-before-function-paren": 0,
            "camelcase": [
                2, {
                    "properties": "nonmethods"
                }
            ]
        }
    }