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
archived due to ageThis issue has been archived; please open a new issue for any further discussionfeatureThis change adds a new feature to ESLintruleRelates to ESLint's core rules
jsdoc can provide useful documentation with IDE integration.
Related ECMAScript feature
no
What type of rule is this?
Enforces a formatting/stylistic preference
Example code
case one: object property
constperson={name: 'ly',// some description op top of propertyage: 18,// some description after property};
case 2: typescriptinterface,shouldalsoworkfortype,enum```typescriptinterfaceOptions{// default value is ['.js', '.ts']
extensions: String[];// default value is ['.js', '.ts']}
case 3: function
// compute sum of two numbersfunctionadd(a,b){}
Why should this rule be in the core instead of a plugin?
Per our rules policies, we can only accept new rules if they relate to new ECMAScript features that reached stage 4 in the preceding 12 months, so this proposal doesn't qualify. You can always make a custom rule and publish a plugin.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
archived due to ageThis issue has been archived; please open a new issue for any further discussionfeatureThis change adds a new feature to ESLintruleRelates to ESLint's core rules
Rule details
jsdoc can provide useful documentation with IDE integration.
Related ECMAScript feature
no
What type of rule is this?
Enforces a formatting/stylistic preference
Example code
case one: object property
case 3: function
Why should this rule be in the core instead of a plugin?
gajus/eslint-plugin-jsdoc#1002 (comment)
Participation
Additional comments
No response
The text was updated successfully, but these errors were encountered: