You shouldn't pad blocks -- you're correct. The eslint rule that enforces this is padded-blocks.

Unfortunately, we had to disable it in 6f75ec3 because eslint 0.19 started incorrectly reporting errors in code that uses ASI. We can re-enable the rule once this issue (eslint/eslint#2336) is fixed.

I'll keep this issue open to remind ourselves to re-enable it once eslint fixes it on their end.

I just put $10 on the issue. If you're willing, please chip in and they may fix it faster.

eslint/eslint#2336

This is fixed in eslint master, but we need to wait for an npm release.

This will be fixed in eslint 1.0.0 and standard 5.0.0. #192

@feross this is still broken (as in, it doesn't throw a warning) in 5.0.2 😭

➜  /tmp  cat test.js     
function test () {

  return 1

}

test()
➜  /tmp  standard --version
5.0.2
➜  /tmp  standard test.js
➜  /tmp  

Confirmed still in 5.0.2.

function test () {

  return 1

}

test()

This is actually a huge breaking change at this point. 22 out of 138 sample repos fail if we enable this rule.

Since this isn't a very important rule -- it doesn't affect code correctness -- I'm inclined to not add this rule back. Or, if we do, it'll have to be in v6.0.0 when/if there are other breaking rules.

But I really want standard to be "done" at some point, so we can stop futzing with the rules and just be productive (which was kinda the whole point of this module ;) Ideally, there won't be a v6.0.0 for a long time.

@feross it was my understanding that this rule was meant to be in place a while ago. I see no reason why we can't just fix up those 22 repositories, the rule has been around long enough that it seems like most users should have been aware of it?

It would seem very odd for us to enforce consistent spacing in objects, but not in functions.
I'd almost be OK with it if we were enforcing:

function a () {
  return 1
}
// OK!

function b () {

  return 2

}
// OK!

function c () {

  return 3
}
// Error! oops

I would really like to see that rule added back. I can volunteer to submit 22 pull requests to get this moving.

As said this rule have been in place for a long time and I think that many people are aware of it, it's easy to miss in one or two places though. Just noticed it in one of my own project, which is what led me to open this issue.

Hopefully I can compile a list of the repos and start working on it during this weekend.

@LinusU Okay, if you get the tests passing, I'm okay with merging this and releasing it in a minor release.

Okay, 22 pull requests sent! Took me just half an hour, nice 😎

First merged! Only 21 to go, I'll edit the first post so that it shows the progress on the issue

@LinusU Second one has just come in 💃 Hyperemitter has updated too.

Super! 🎆

I've updated the list 👏

In terms of @mcollina 's other ones, I'll ping him for access when he gets back. But consider them done.

@LinusU, awesome work.

I'm back ;). On this.

Only two repos to go now 👍

@feross There are two holdouts, can we go ahead anyway?

LGTM

It's only npm/docs that's holding out now

Sure, let's go ahead.

Released as 5.2.0.

Cool 👍

Could this be reopened until it's documented somewhere (and fixed)? Having to hunt down closed issues to see why the error is there since nothing like this is document is a bit weird...

@franciscop Padded blocks are disallowed in standard. Not sure what your issue is. If you have a new bug to report, please open a new issue.