Dmitry

`IndexedAccessType` is a different kind of node than an `IndexSignatureDeclaration`. So your case should look like ``` case ts.SyntaxKind.IndexedAccessType: return this._compileIndexedAccessType(node as ts.IndexedAccessTypeNode); ``` You can learn more about that...

You can do it fairly easily using the [chokidar](https://www.npmjs.com/package/chokidar-cli) module: ``` chokidar src/types/*.ts -c 'ts-interface-builder -o src/ti {path}' ```

@fastfrwrd, since you added the `--inline-imports` option, do you have any suggestions here?

Implementing specific generics like `Pick` seems reasonably straightforward. Implementing generics generally (or even just mapped types generally) is probably doable too, but requires a much deeper understanding of typescript internals.

There are two generic types handled: `Array` and `Promise` (the latter is just treated as `T`, which happens to be helpful for some cases). See `_compileTypeReferenceNode` method. That's where the...

Could you include an example of where it would be useful? In particular, it would help decide how to support such signatures, or if we only need to be able...

Perhaps you are right. But that's why I am asking. Call signatures don't make sense for a data descriptor of the kind that you might consider using JSON Schema validator...

What's the typescript file being compiled?

So this mainly seems a problem with `ts-interface-builder` lacking support for namespaces (perhaps would be fixed by #28?) The use of `enumlit` seems out of place, so that may be...