-
-
Notifications
You must be signed in to change notification settings - Fork 163
v10.3.0-11.2.0 are broken due to missing dependency escape-regex-string #314
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
pgoldrbx
referenced
this issue
Jul 6, 2019
…r messages when suggesting tags to reject or replace (#302) * feat(check-tag-names): allow rejecting normally valid tag names and/or providing custom error messages when suggesting tags to reject or replace (fixes #108) Reporting normally valid tags may be of interest for tags like `@todo`. This is implemented by allowing the user to set targeted `tagNamePreference` tags to `false` or to an object with only a `message` and no `replacement` Custom messages for `check-tag-names` are implemented by allowing the user to set targeted `tagNamePreference` tags to an object with `message` and `replacement` (mirroring `preferredTypes` behavior). Note that for other rules leveraging `tagNamePreference` (via `utils.getPreferredTagName`) to find the user's preferred tag name, the `replacement` will be used in the likes of error messages but not the `message`. Also, for various (param, return, and description-related) rules which have used `tagNamePreference` (via the `utils.getPreferredTagName` utility), report to user if they have blocked (probably inadvertently) and not indicated a replacement for the relevant tag needed by the rule in the `tagNamePreference` setting. Also, ensure `require-param-name` and `check-examples` report preferred tag name (not necessarily `param` or `example`, respectively) and err if `example` is a rejected tag
Ugh, sorry about that... Too used to Rollup routines pulling it all together (and linting rules to complain about it). Plan to push out a fix shortly. |
🎉 This issue has been resolved in version 11.2.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Closed
1 task
brettz9
added a commit
to brettz9/eslint-plugin-jsdoc
that referenced
this issue
Jul 7, 2019
* master: docs: correct docs refactor: change option extraction codes refactor: leverage `settings` property from `iterateJsdoc.js` for consistent settings access docs: update docs feat(`require-example`): move settings to options feat(`require-jsdoc`): move settings to options feat(`valid-types`): move settings to options feat(`require-returns`): move settings to options fix(`check-examples`): make `escape-regex-string` a dependency, as it should have been (fixes gajus#314) # Conflicts: # README.md # src/rules/validTypes.js # test/rules/assertions/validTypes.js
🎉 This issue has been resolved in version 15.9.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
#302 introduced dependency
escape-regex-string
for parsing@example
tags. However this package was added todevDependencies
instead of to the packagedependencies
. As a result, all project development and tests are passing but the package fails for downstream consumers.This was first released in version 10.3.0 and persists still in the current release v11.2.0
The text was updated successfully, but these errors were encountered: