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
How to remove redundant newlines on trimmed members?
I want to trim internal members in my public release.
Let's say a sample .d.ts file is as follow
export class SampleClass { /** @internal */ private _member1; /** @internal */ private _member2; /** @internal */ private _member3; /** @internal */ private _member4; /** @internal */ private _member5; /** @public */ constructor(); /** @public */ public member1; /** @public */ public member2; }
My config file is an initially created one, and I just update dstRollup part as follow
"dtsRollup": { "enabled": true, "untrimmedFilePath": "<projectFolder>/dist/sdk/splat/sdk/index.d.ts", "publicTrimmedFilePath": "<projectFolder>/dist/sdk/splat/splat.d.ts", "omitTrimmingComments": true },
The generated release has multiple newlines for the trimmed internal members
export class SampleClass { /** @public */ constructor(); /** @public */ public member1; /** @public */ public member2; }
Expected result:
Actual result:
Please answer these questions to help us investigate your issue more quickly:
@microsoft/api-extractor
node -v
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Summary
How to remove redundant newlines on trimmed members?
Repro steps
I want to trim internal members in my public release.
Let's say a sample .d.ts file is as follow
My config file is an initially created one, and I just update dstRollup part as follow
The generated release has multiple newlines for the trimmed internal members
Expected result:
Actual result:
Details
Standard questions
Please answer these questions to help us investigate your issue more quickly:
@microsoft/api-extractor
version?node -v
)?The text was updated successfully, but these errors were encountered: