Add a fixer for the 'curly' rule

[calebegg]

No description provided.

[ajafff]

this variable is never used

[calebegg]

Fixed

[ajafff]

This can be simplified to:

const positionToAddOpenBrace = statement.pos;

[calebegg]

whoa

[ajafff]

const match = /\n([\t ])/.exec(node.getFullText(this.sourceFile)); // determine which character to use (tab or space)
const indentation = match === null ? "" : match[1].repeat(ts.getLineAndCharacterOfPosition(node.getStart(this.sourceFile)).character); // indentation should match start of statement

[calebegg]

Done

[ajafff]

we should try to infer the correct line ending. See

tslint/src/rules/eoflineRule.ts

Line 49 in 02dd308

fix = Lint.Replacement.appendText(length, sourceFile.text[lines[1] - 2] === "\r" ? "\r\n" : "\n");

or

tslint/src/rules/orderedImportsRule.ts

Lines 365 to 377 in 02dd308

	private getEolChar(): string {
	const lineEnd = this.sourceFile.getLineEndOfPosition(0);
	let newLine;
	if (lineEnd > 0) {
	if (lineEnd > 1 && this.sourceFile.text[lineEnd - 1] === "\r") {
	newLine = "\r\n";
	} else if (this.sourceFile.text[lineEnd] === "\n") {
	newLine = "\n";
	}
	}
	return newLine === undefined ? ts.sys.newLine : newLine;
	}
	}

[calebegg]

My years away from Windows have softened me.

I tried to add a test but the test system seems to balk at CRLFs.

[ajafff]

There are already some tests using CRLF. At least the ones in test/rules/linebreak-style/*.
The line endings may be overridden by your editor because of .editorconfig or by git because of .gitattributes.
Your code looks good. I don't think this test case is super important.

[ajafff]

better name it createMissingBraceFix or similar

[calebegg]

Done

[ajafff]

Thanks @calebegg