We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I only want to make sure that when type is native it is one of the following: boolean, number, string, Object, Array, Date, RegExp.
I do want to allow types that refer to typedef, e.g. foo~something.
typedef
foo~something
Based on the current https://github.com/jscs-dev/jscs-jsdoc#checktypes description, it appears that this rule disallows use of custom types.
The text was updated successfully, but these errors were encountered:
It should not. It just checks that your types (native/custom whatever) are parseable. Here you can try it: http://kuniwak.github.io/jsdoctypeparser/
Atm, jsdoc using v1.4, and upgrade in progress. And I was trying to implement it since the end of aug. Guess it's time to do this.
foo~something is a valid jsdoc type so the rule should NOT report it.
Ref: jscs-dev/node-jscs#1577
Sorry, something went wrong.
No branches or pull requests
I only want to make sure that when type is native it is one of the following: boolean, number, string, Object, Array, Date, RegExp.
I do want to allow types that refer to
typedef
, e.g.foo~something
.Based on the current https://github.com/jscs-dev/jscs-jsdoc#checktypes description, it appears that this rule disallows use of custom types.
The text was updated successfully, but these errors were encountered: