We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hello !
Currently using ts-patch in a library to copy jsdoc in a string within an annotation. My tsconfig.json file looks like
tsconfig.json
"plugins": [ { "transform": "./src/reflection/add-jsdoc-to-function-configs.ts" } ]
So it does not refer a package name but directly a source file. It uses the really useful transformer entry point.
Have seen your recent pull request about the 5.3 support and seen this line in plugin-creator.ts
plugin-creator.ts
this.needsTscJsDocParsing = this.plugins.some(plugin => plugin.packageConfig?.tscOptions?.parseAllJsDoc === true);
Wondered if we could enable the support of full jsdocs parsing using a syntax like
"plugins": [ { "transform": "./src/reflection/add-jsdoc-to-function-configs.ts", "parseAllJsDoc": true } ]
where the property parseAllJsDoc could be a direct child of the PluginConfig interface ?
parseAllJsDoc
PluginConfig
Thanks
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hello !
Currently using ts-patch in a library to copy jsdoc in a string within an annotation.
My
tsconfig.json
file looks likeSo it does not refer a package name but directly a source file. It uses the really useful transformer entry point.
Have seen your recent pull request about the 5.3 support and seen this line in
plugin-creator.ts
Wondered if we could enable the support of full jsdocs parsing using a syntax like
where the property
parseAllJsDoc
could be a direct child of thePluginConfig
interface ?Thanks
The text was updated successfully, but these errors were encountered: