Missing parsed information

Parser unfortunately doesn’t return full information about parsed code.

Right now I know about missing

• async flag (https://github.com/buehler/node-typescript-parser/issues/66)
• isStatic flag (https://github.com/buehler/node-typescript-parser/issues/43)
• propertyIsOptional flag (e.g. { myProperty?: string } )
• while parsing property of type Object (e.g. { myProperty: { innerPropery: string } }, the type is not fully parsed and returns values like {\n email: string\n } I can parse finish parsing by recursive call of parser.parseSource(), but it’s very inconvenient

Can we get this fixed, please?

[ondratra]

@buehler Imho it is false. In case you would like to parse TS file and then ‘reconstruct them’ from parsed info you could actually get different code. Some examples follow.

When async is explicitly stated it always has to return Promise. Even TS compiler will force you to return Promise.

async function asyncFunction(): Promise<string> {
    return 'result'
}

This function is not explicitely stating async yet it’s returning Promise

function indirectAsyncFunction(): Promise<string> {
    return asyncFunction()
}

This async function calls awaits on another async function.

async function complexAsyncFunction(): Promise<string> {
    return await asyncFunction()
}

Notice difference between indirectAsyncFunction() and complexAsyncFunction(). If you add extra async keyword in front of indirectAsyncFunction without further editation(adding await for asyncFunction()) it would actually return Promise<Promise<string>>.

Because of that I think parser should return async flag only for function that explicitly state it.

[buehler]

I’m going to close this issue in favor to propper issues for each feature 😃