Closed chris48s closed 3 years ago
V31 switched to a new version of comment-parser
which helps preserve whitespace but which still has a few hiccups to work out (also #669), so good to have reported this. I filed https://github.com/syavorsky/comment-parser/issues/112 , so I think we are now blocking on that.
:tada: This issue has been resolved in version 31.0.6 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Consider the following example:
Using 30.7.13 or lower, this is fine, but as of >=31.0.0 this now throws
Note this example (not using arrow syntax for the default):
is fine with either version.
Is this a bug, or do I need to make a change to accommodate this version?
Expected behavior
Example above (using arrow function) should be valid (I think?)
Actual behavior
It was considered valid by <=30.7.13
ESLint Config
Disabling these rules silences the error
I've included the full output of
eslint --print-config
at the end of the issueESLint sample
Environment
eslint-plugin-jsdoc
version: >=31.0.0Full output of
eslint --print-config
: