tsfmt and JSX

[myitcv]

I've been using tsfmt to format TypeScript code. I believe this uses the pretty-printer from core compiler service.

But I've hit upon the following issue when formatting:

/// <reference path="typings/tsd.d.ts" />

import React = require("react");

function test(): any {
    return <span>This is a test</span>;
}

the output is:

/// <reference path="typings/tsd.d.ts" />

import React = require("react");

function test(): any {
    return <span>This is a test< /span>;
}

Notice the problematic < /span>.

The former compiles, the latter does not:

$ ./node_modules/.bin/tsc --jsx react --module system test.tsx
test.tsx(6,34): error TS1003: Identifier expected.
test.tsx(6,35): error TS1005: '>' expected.
test.tsx(9,1): error TS17002: Expected corresponding JSX closing tag for 'span'.

Any thoughts?

[myitcv]

Another related example:

/// <reference path="typings/tsd.d.ts" />

import React = require("react");

function test(): any {
        let v: number = 5;
    return <span>{ v }</span>;
}

is formatted as:

/// <reference path="typings/tsd.d.ts" />

import React = require("react");

function test(): any {
    let v: number = 5;
    return <span>{ v } < /span>;
}

[RyanCavanaugh]

This is a tsfmt bug.

Here: https://github.com/vvakame/typescript-formatter/blob/master/lib/formatter.ts#L14

The source file the compiler gets is being created with the '.ts' extension, which means it's consumed using the regular TypeScript grammar. tsfmt needs to be able to support passing a '.tsx' file extension when appropriate so that expressions of the form <T>x are interpreted as JSX tags rather than type assertions.

[myitcv]

@RyanCavanaugh - thanks very much.

[vvakame]

ah, I understand. thank you!