Aljeksej Jaroševič
Aljeksej Jaroševič
Unfortunately it's a functionality coming from `jscs`. /cc @mdevils
All we can do in plugin is to move all rules to root. So we would have something like: ``` js { jsdocCheckTypes: ... jsdocEnforceExistance: ... // etc... } ```...
Does `checkAnnotations: { extra: { "returns": null } }` to deny `@returns` would be fine?
I should say that currently you allowing both when you using closure or jsdoc3 tag set: https://github.com/jscs-dev/jscs-jsdoc/blob/1d6e20f588564fa61f8794b9d1301702abdfa4be/lib/tags/jsdoc3.json#L64-L65 But I'm not sure that this is right. Closure compiler uses `@return`: https://developers.google.com/closure/compiler/docs/js-for-compiler#tag-return...
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...
The idea was to add a preset with all `apiDoc` tags. But it's useless until there is no multipreset support. #69 Atm you can do it manually (see http://jscs.info/rule/jsDoc#checkAnnotations): ```...
Can you show a function?
Actually to understand a problem I need just all blocks and scopes inside your function. Can you left just ifs, whiles, switch-cases, functions and show your func?
Great! I'm almost sure it's a bug in doc to code matching logic. Thanks for your time and code ;-)
@cowwoc I have a problem. I can't repeat this ;-) Can you try to clone gist and test in your env? https://gist.github.com/zxqfox/4754742b9eb412560535