Parameter type validation for JSDuck should allow primitives types

[jdforrester]

Per the JSDuck documentation, values can be objects or primitive values. It's useful to distinguish whether you're expecting an object or a primitive. However, the latter case does not work.

Primitives types which fail

• {boolean}
• {number}
• {string}

  Equivalent objects which work

• {Boolean}
• {Number}
• {String}

[Krinkle]

:+1:

[qfox]

Guys, both of them should works, just choose what you need. http://jscs.info/rule/jsDoc.html#checktypes

If you want to use both of them in the same project — seems like we need new rule value. Or just try to use checkTypes: true.

[Krinkle]

I think checkType: "strictNativeCase" will do what we want. We don't actually use boxed primitives. Allowing both only causes confusion and wasted human efforts to fix them to be lowercased instead. This rule would allow us to enforce that.

Thanks!

[jdforrester]

Sorry, this can be marked as resolved.