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
{{ message }}
This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
This isn't exactly a bug, so I'll mark as an enhancement. All the JSDoc documentation shows two ways to write out comments:
One line: /** Some comment here */
Multi-line:
/**
* Some comment
* more comments
*/
TSLint currently (v3.6.0) allows both of the following:
Expected multi-line
/**
* Some comment
* More info
*/
Unexpected multi-line
/** Some comment
* More info
*/
I don't think this breaks JSDoc, but it isn't expected and from a styling point of view, mixing them isn't ideal. Can the rule enforce the expected styling?
The text was updated successfully, but these errors were encountered:
@ajafff I would think this would be the default behavior if jsdoc-format was turned on. However, it might make sense to accept configuration of the rule. I see 2 options:
enforce my "expected multi-line"
enforce my "unexpected multi-line"
Therefore you don't get a mixture in your project, but you are flexible to someone's style considering it doesn't break the typical js-doc tool.
This isn't exactly a bug, so I'll mark as an enhancement. All the JSDoc documentation shows two ways to write out comments:
/** Some comment here */
TSLint currently (v3.6.0) allows both of the following:
I don't think this breaks JSDoc, but it isn't expected and from a styling point of view, mixing them isn't ideal. Can the rule enforce the expected styling?
The text was updated successfully, but these errors were encountered: