Expose API for getting JSDoc nodes in TypeScript files

Closure adds various semantic JSDoc annotations that aren't currently modeled by TypeScript, such as @export (unrelated to TS export) and @nosideeffects.
https://developers.google.com/closure/compiler/docs/js-for-compiler#overview

As part of our tool chain to run TypeScript through Closure we'd like to be able to munge these via the TypeScript API. It appears TypeScript gathers JSDoc comments when parsing JavaScript -- is there a good reason to not gather these in TypeScript as well?

Specifically, I believe my suggestion amounts to removing the "if" statement in the below code (though I'm not certain this is the right place) in parser.ts:

        function addJSDocComment<T extends Node>(node: T): T {
            if (contextFlags & NodeFlags.JavaScriptFile) {
                ...all of the code is in here...
            }
        }

Commencez dans parser.ts, au niveau de addJSDocComment, et examinez comment la garde NodeFlags.JavaScriptFile limite la collecte de JSDoc. Comparez le chemin d’analyse JavaScript existant avec l’analyse des fichiers TypeScript et consultez la discussion de l’issue pour déterminer la limite d’API prévue. Le travail est terminé lorsque les nœuds JSDoc des fichiers TypeScript sont accessibles via l’API TypeScript, y compris les annotations Closure telles que @export et @nosideeffects.