-
-
Notifications
You must be signed in to change notification settings - Fork 163
jsdoc/valid-types throwing warning when we use import syntax #593
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
Labels
Comments
You currently need to have cc: @doberkofler |
brettz9
added a commit
to brettz9/eslint-plugin-jsdoc
that referenced
this issue
Jun 23, 2020
…fault to `typescript` when `typescript-eslint/parser` is on; fixes gajus#593
brettz9
added a commit
to brettz9/eslint-plugin-jsdoc
that referenced
this issue
Jun 23, 2020
…fault to `typescript` when `typescript-eslint/parser` is on; fixes gajus#593
brettz9
added a commit
to brettz9/eslint-plugin-jsdoc
that referenced
this issue
Jun 23, 2020
…fault to `typescript` when `typescript-eslint/parser` is on; fixes gajus#593
brettz9
added a commit
to brettz9/eslint-plugin-jsdoc
that referenced
this issue
Jun 23, 2020
…fault to `typescript` when `typescript-eslint/parser` is on; fixes gajus#593
🎉 This issue has been resolved in version 28.5.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Was wondering what would be the right syntax if it's not a bug? Example below:
The text was updated successfully, but these errors were encountered: