New option in "object-curly-spacing" for empty objects

Tell us about your environment

• ESLint Version: v3.8.0
• Node Version: v6.7.0
• npm Version: v3.10.7

What parser (default, Babel-ESLint, etc.) are you using?

Default

Please show your full configuration:

{
  "rules": {
    "object-curly-spacing": ["error", "never"]
  }
}

What did you do? Please include the actual source code causing the issue.

var a = { }

What did you expect to happen?

I expected that the rules should complain about the stray space between the curly braces { }

I also think it would be a good idea to add a separate config for empty objects, since I think that people who have this rule set to “always” still doesn’t want any whitespace inside empty objects.

What actually happened? Please include the actual, raw output from ESLint.

No error was raised.

(Note: Re-opening https://github.com/eslint/eslint/issues/7380 for discussion, as suggested)

[not-an-aardvark]

I’m going to go ahead and mark this as “evaluating” again – the accepted label was originally added when this was considered a bug, but now it seems to be proposing a new option.

[pmcelhaney]

I don’t care about the difference between { } and {} but I work with someone who refuses to let it go and continues to clog up pull requests with bike shed comments.

I’m going to work on a PR to make the treatment of empty objects an option.

• spaceInEmptyObject: "always": Require a space inside of an empty object literal ({ } is valid)
• spaceInEmptyObject: "never": Disallow a space inside of an empty object literal ({} is valid)

If spaceInEmptyObject is not specified, either { } or {} is allowed.

If you don’t hear from me within the next week, assume that I got too busy and gave up on the idea.