Clarify ident rule about tslint

[ashwinr]

indent checks for indentation consistency within statement blocks. Currently, a tab character is treated as 4 spaces, but we can make it configurable if necessary. Take a look at the indentation test if you really want to understand how the rule works.

[Bartvds]

I think there is a bug that was part of my confusion, looks related to the one-line literals:

With this rule:

"indent": [true, 4],

In this snippet (with tabs)

        getKey(label:string, keyTerms?:any):string {
            return xm.jsonToIdent([label, keyTerms ? keyTerms : {}]);
        }

I get these 2 errors (line 75 is the indented line):

>> src/git/GitAPICached.ts[75, 27]: unexpected tab width: expected 16, got 0
>> src/git/GitAPICached.ts[75, 34]: unexpected tab width: expected 16, got 0

[Bartvds]

This one is interesting as well. This the content of a single file:

module xm {
    export function callAsync(callback, ...args:any[]) {
        process.nextTick(() => {
            callback.apply(null, args);
        });
    };
}

With this error: (line 6 is is next-to-last-one with the };

>> src/xm/callAsync.ts[6, 3]: unexpected tab width: expected 4, got 0

Notice the }; is my mistake, the semicolon doesn't belong there (as the brace is from a named function). If I remove the semicolon the rule passes.

[ashwinr]

Fixed the indentation rule to allow one-line literals always. so, the first example above should work.

[ashwinr]

there's not much we can do about the second one. the single semi-colon is treated as an empty statement, and tslint complains about it not indented correctly (which is a valid complaint, IMHO). In general, we advise tslint to run after the tsc compilation succeeds, so we don't get tripped up by compiler errors, but there's not much we can do in this particular case.

[Bartvds]

Cool, I understand. I had tslint before compilation, as it is a lot faster then compiling. But I can see how that'd could go wrong, I'll swap it.

Note the noempty doesn't warn about this particular case though (in my 0.2.1)

[ashwinr]

but there's no empty block in your example, right?

[Bartvds]

Ooops, you are right!

I was confused with your mention of 'empty statement' (which there is between the closing brace and the semicolon, but that's not this rule).

[ashwinr]

cool :)