-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
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
Force @return or @returns #167
Comments
Does |
I should say that currently you allowing both when you using closure or jsdoc3 tag set: jscs-jsdoc/lib/tags/jsdoc3.json Lines 64 to 65 in 1d6e20f
But I'm not sure that this is right. Ref: #76 |
Semantically, @return does not make sense. You don't give a command to the function. You describe what it does. It returns a value.
|
Has any decision been taken regarding this since? |
I'd suggest to wait "multi-sets" (when you'll be able to use jsdoc3 with googleclosure addon) and then cleanup tag sets (e.g. remove returns from googleclosure set). I think we shouldn't remove What you think? |
A rather general suggestion is to remove https://github.com/jscs-dev/jscs-jsdoc#checkannotations entirely. This rule is too broad. Instead, allow granular control (allowed, not allowed), case sensitive, control of all the supported tags. |
Have a rule that forces user to use either
@return
tag or@returns
.The text was updated successfully, but these errors were encountered: