You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using this plugin to generate .d.ts files from .ts ones that I manually populate, mostly because I'd like to end up with declaration files that serve as documentation for the whole thing without requiring any special code editor/ide.
So I normally have a block-comment, a declaration following it, and I'd like to have an empty new line between these, so that the resulting file doesn't look crammed. To this regard, I'm hitting the wall on the writeOutput function, maybe there's some inline way of doing it rather than messing with the source.
If possible, I'd also like to use regular block-comments. I'm not a vs-code user myself and have no intention of learning their markup, so it would be great if the plugin wouldn't just ignore the comments I write just because these don't start with /**, and would otherwise like to write these wherever I find convenient other than just as fixed blocks before the declarations themselves.
I'll keep looking at the source code to see if I can get there with minimal or no intervention to it, but would appreciate any comments that would allow me doing this.
Thanks,
Suggested solution
Don't know the source enough yet to comment on that
Description
Hi,
I'm using this plugin to generate
.d.ts
files from.ts
ones that I manually populate, mostly because I'd like to end up with declaration files that serve as documentation for the whole thing without requiring any special code editor/ide.So I normally have a block-comment, a declaration following it, and I'd like to have an empty new line between these, so that the resulting file doesn't look crammed. To this regard, I'm hitting the wall on the
writeOutput
function, maybe there's some inline way of doing it rather than messing with the source.If possible, I'd also like to use regular block-comments. I'm not a vs-code user myself and have no intention of learning their markup, so it would be great if the plugin wouldn't just ignore the comments I write just because these don't start with
/**
, and would otherwise like to write these wherever I find convenient other than just as fixed blocks before the declarations themselves.I'll keep looking at the source code to see if I can get there with minimal or no intervention to it, but would appreciate any comments that would allow me doing this.
Thanks,
Suggested solution
Don't know the source enough yet to comment on that
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: