global-require should allow `require` statements as properties in object literals

eslint version: ^1.4.1

rule config: "global-require": 1

Assuming I have a folder structure like this

/ app 
   / validators
      - validate-string.js
      - validate-number.js
      - index.js

And /app/validators/index.js

// index.js
module.exports = {
  string: require('./validate-string'),           // this violates global-require rule
  number: require('./validate-number')
};

It does not make sense to me that this is a violation.

[nzakas]

@jamestalmage you can always create your own rule to do this. The fact is, once you add in enough exceptions then the rule is no longer doing what it was intended to do, and that’s when people get confused. That’s why we allow custom rules - you don’t have to convince us, just write a rule that does exactly what you want.

[ilyavolodin]

Agree. This rule was created to make sure that all require statements are clearly marked at the top of the file. If you don’t follow that pattern - just turn off this rule.