Add `requireParamTypes` option to the `valid-jsdoc` rule

While using babel-plugin-typecheck, I realized that specifying parameter types is redundant, as they can be retrieved from the Flow syntax.

See TypeDoc’s DocComments for further reference about the accepted documentation format with requireParamTypes set to false. The default value of requireParamTypes should be true.

[ilyavolodin]

@kripod I’m not sure if you are explaining ideal situation or what is happening right now. Are there any tools out there that would generate documentation by combining jsDoc and Flow? And in general, ESLint doesn’t naively support Flow. It’s only supported through babel-eslint. So we would need much more generic scenario to consider adding an option to disable typing for jsDoc in the core. Otherwise, this might be a good request to add to eslint-plugin-flowtype

[vitorbal]

Hi @kripod, thanks for your submission. Please take a moment to read over our guide on proposing rule changes: http://eslint.org/docs/developer-guide/contributing/new-rules

Specifically, we do require proposers to implement their suggestions if accepted, so your willingness to implement it is a key decision point.

Currently, the team is very focused on improving compatibility between JSCS and ESLint, so if you are not willing to work on a PR for this, I’m afraid there is a low chance this will end up getting accepted.