Comments on: Generate Documentation for TypeScript https://codebelt.github.io/blog/typescript/generate-documentation-for-typescript/ Manage Your Code Snippets with codeBelt | Code Examples / Tutorials / Articles Wed, 14 Feb 2018 05:52:52 +0000 hourly 1 https://wordpress.org/?v=4.9.10 By: Antonio https://codebelt.github.io/blog/typescript/generate-documentation-for-typescript/#comment-30509 Thu, 02 Oct 2014 01:03:42 +0000 https://codebelt.github.io/blog/?p=1314#comment-30509 He obviously doesn’t have solution other than the ability to bitch and moan.

]]> By: robert https://codebelt.github.io/blog/typescript/generate-documentation-for-typescript/#comment-22164 Sat, 25 Jan 2014 15:22:54 +0000 https://codebelt.github.io/blog/?p=1314#comment-22164 Thanks for the feedback. If you can show me an better/easier way to generate documentation for TypeScript. I’m all ears.

]]> By: Matthew https://codebelt.github.io/blog/typescript/generate-documentation-for-typescript/#comment-22143 Fri, 24 Jan 2014 00:46:02 +0000 https://codebelt.github.io/blog/?p=1314#comment-22143 No offense, but this isn’t a very good solution…

/**
* @property isEnabled
* @type {boolean}
* @default false
* @protected
*/
public isEnabled:boolean = false;

The great thing about JSDoc for JavaScript is that it can take standard-looking, minimal comments and generate relatively useful documentation. If you have to basically rewrite every declaration into your doc comments, then you either can’t use refactoring tools or have to deal with the fact that your documentation is going to get out of date fast.

]]>