daisy-chain indentation leads to over-indentation

Using this via https://github.com/enginespot/js-beautify-sublime

Expected:

object
.foo()
.bar();

Actual:

object
  .foo()
  .bar();

To illustrate the problem: the current indenting can lead to EOFs like this:

      });
    });
})();

That looks like an error to me, and will prompt me to look for the cause – or worse, make me blind to the real ones =(

[arthur5005]

I have to +1 this request, this is especially handy when working with Promises.

Promise.resolve()
.then(function() {
  return foo.bar()
})
.then(function() {
  return foo.baz();
})
.then(function() {
 //...
}) //...
//...

This chaining can continue for a while, especially when writing a more involved api end point, and by the time you’re looking at the bottom you’re constantly thrown off guard with how the indentation finishes relative to something close by.

I believe it’s important that all closing indentation be one level of depth difference from the next nearest.

[klarkc]

+1 This is leading to Expected exactly one space between '{a}' and '{b}' errors in jslint.

Example:

gulp.task('changelog', function () {
    return gulp.src('CHANGELOG.md', {
            buffer: false
        })
        .pipe(conventionalChangelog({
            preset: 'angular' // Or to any other commit message convention you use.
        }))
        .pipe(gulp.dest('./'));
});

Errors:

4   Expected 'buffer' at column 9, not column 13.    buffer: false
5   Expected '}' at column 5, not column 9.  })

Correct way (for jslint):

gulp.task('changelog', function () {
    return gulp.src('CHANGELOG.md', {
        buffer: false
    })
        .pipe(conventionalChangelog({
            preset: 'angular' // Or to any other commit message convention you use.
        }))
        .pipe(gulp.dest('./'));
});