Certain types can produce implicit 'any' declaration output

[DanielRosenwasser]

Apparently this became a bug in TypeScript 1.4 and we never noticed.

export let x: (foo) => number;

Compile this with --declaration and module: esnext

Expected:

export let x: (foo: any) => number;

Actual:

export let x: (foo) => number;

[DanielRosenwasser]

Actually, it's really

• Function type parameters
• Constructor type parameters
• Property signatures
• Any parameter whose grandparent is an anonymous object type literal.

Here's a decent test case:

export type A = (foo1, foo2) => number;
export type B = new (foo1, foo2) => string;
export type C = {
    foo;
    bar(barParam);
    baz(bazParam1, bazParam2);
}

[weswigham]

I think I have this fixed, by chance, in the upcoming declaration transformer.

[DanielRosenwasser]

Awesome - what is the name of your branch?

[weswigham]

declaration-emitter-refactor on my fork, I believe. Tests still aren't clean yet, though (hence why the pr isn't open).