chore(deps): update dependency eslint-plugin-jsdoc to v35 #83
+109
−57
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
☁️ Nx Cloud ReportAttention: This version of the Nx Cloud GitHub bot will cease to function on July 1st, 2023. An organization admin can update your integration here. We didn't find any information for the current pull request with the commit e6640d6. Check the Nx Cloud Github Integration documentation for more information. Sent with 💌 from NxCloud. |
renovate
bot
force-pushed
the
renovate/eslint-plugin-jsdoc-35.x
branch
4 times, most recently
from
3597918
to
4235828
Compare
renovate
bot
force-pushed
the
renovate/eslint-plugin-jsdoc-35.x
branch
4 times, most recently
from
492695e
to
5920913
Compare
renovate
bot
force-pushed
the
renovate/eslint-plugin-jsdoc-35.x
branch
from
5920913
to
51617f4
Compare
renovate
bot
force-pushed
the
renovate/eslint-plugin-jsdoc-35.x
branch
from
51617f4
to
e1a1def
Compare
renovate
bot
force-pushed
the
renovate/eslint-plugin-jsdoc-35.x
branch
2 times, most recently
from
a8d202d
to
ffc8179
Compare
renovate
bot
force-pushed
the
renovate/eslint-plugin-jsdoc-35.x
branch
2 times, most recently
from
c7c626c
to
9b3ec4a
Compare
renovate
bot
force-pushed
the
renovate/eslint-plugin-jsdoc-35.x
branch
from
9b3ec4a
to
ec339e7
Compare
renovate
bot
force-pushed
the
renovate/eslint-plugin-jsdoc-35.x
branch
from
ec339e7
to
b3591b4
Compare
renovate
bot
force-pushed
the
renovate/eslint-plugin-jsdoc-35.x
branch
from
b3591b4
to
e6640d6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
31.6.1->35.5.1Release Notes
gajus/eslint-plugin-jsdoc (eslint-plugin-jsdoc)
v35.5.1Compare Source
Bug Fixes
jsdoccommentversion for now; fixes #772 (c9b854b)v35.5.0Compare Source
Features
require-returns-check: addexemptGeneratorsoption (default on for typescript mode) to allow[@returns](https://togithub.com/returns)to be present even withoutreturn(8ef41a1)v35.4.7Compare Source
Bug Fixes
require-returns: handle contexts TSFunctionType, TSMethodSignature, MethodDefinition; fixes #767 (fdca227)v35.4.6Compare Source
Bug Fixes
require-param: if adding params, convert single-line block to multiline; fixes #771 (641cdee)v35.4.5Compare Source
Bug Fixes
valid-types: allow and require types on[@extends](https://togithub.com/extends)for TypeScript as used in docs (and not name) (6989699)v35.4.4Compare Source
Bug Fixes
tag-lines: allowanyintags[tag].linesoption to allow lines per tag when otherwise blocked (52d7eff)v35.4.3Compare Source
Bug Fixes
check-line-alignment: preserve carriage returns; fixes #745 (27521d2)v35.4.2Compare Source
Bug Fixes
check-examples: auto-disableno-empty-functionrule for expression checking; clear it is a no-op in this context (5a928db)v35.4.1Compare Source
Bug Fixes
no-missing-syntax: fix message; closes #761 (317674c)v35.4.0Compare Source
Features
messageoptions formatch-description; fixes #688 (7257e44)v35.3.2Compare Source
Bug Fixes
throwmissing[@throws](https://togithub.com/throws); fixes #722 (f7c8038)v35.3.1Compare Source
Bug Fixes
v35.3.0Compare Source
Features
match-namerule; fixes #509 (eff90bd)v35.2.0Compare Source
Features
no-missing-syntax,no-restricted-syntax, etc.: assumeanycontext ifcontextomitted (2dcd9ad)v35.1.3Compare Source
Bug Fixes
require-jsdoc:exemptEmptyFunctionsoption could trigger problematic return value checking behavior with no-argument functions (3089a92)v35.1.2Compare Source
Bug Fixes
v35.1.1Compare Source
Bug Fixes
jsdoc-type-pratt-parser(liberalizes ID start to support underscores and start/continue to support other Unicode) (1a6de5e)v35.1.0Compare Source
Bug Fixes
no-missing-syntax,no-restricted-syntax: support "any" with comment including global comments (dc641cc)Features
jsdoc-type-pratt-parser(647d47e)v35.0.0Compare Source
Bug Fixes
multiline-blocks: Enable (noZeroLineTextandnoFinalLineTextwill apply by default) (b81e25d)BREAKING CHANGES
multiline-blocks: Should have been enabled by defaultAlso adds newer rules to doc listing
v34.8.2Compare Source
Bug Fixes
check-line-alignment: add multiline type workaround (#744); fixes part of #743 (9928298)v34.8.1Compare Source
Bug Fixes
tag-lines: avoid false positive for "never" when line break occurs in the middle of a tag description. (3496011)tag-lines: ensure a middle-of-block empty line doesn't suppress "always" errors (33aa921)v34.8.0Compare Source
Features
tag-lines: addtagsoption to override behavior on a tag-specific basis (including only applying to tag(s)); fixes #734 (6e5e76d)v34.7.0Compare Source
Features
multiline-blocks: addnoFinalLineTextoption; fixes #738 (03d3f40)v34.6.3Compare Source
Bug Fixes
multiline-blocks: fix merging of lines to prevent removal of spaces, though removing where needed (9af6e36)v34.6.2Compare Source
Bug Fixes
multiline-blocks: ensurenoZeroLineTextchecks whennoMultilineBlocksistruebut not matching; fixes #737 (19f60ac)v34.6.1Compare Source
Bug Fixes
no-multi-asterisks: avoid false positives and erring in fixer of single line blocks; fixes #735 (355da58)v34.6.0Compare Source
Features
no-multi-asterisksrule to prevent multiple asterisks with middle delimiters or at end of blocks (8848246)v34.5.0Compare Source
Features
multiline-blocks: allow control of how and whether jsdoc blocks can be expressed as single or multiple line blocks (06bbf37)v34.4.0Compare Source
Features
tag-line; fixes #93 (851e3fe)v34.3.0Compare Source
Features
check-values: ensure[@variation](https://togithub.com/variation)is a positive integer (56577ce)v34.2.2Compare Source
Bug Fixes
check-param-names: adjusts line numbers to be nearer problematic item (e6c9ab2)no-missing-syntax: pass in missingcomment(a977896)v34.2.1Compare Source
Bug Fixes
require-description,require-example: for missing description, use tag line number (310ea75)v34.2.0Compare Source
Features
no-bad-blocks: addpreventAllMultiasteriskBlocksboolean option to allow reporting of any multi-asterisked multiline comments (9669fc3)v34.1.0Compare Source
Features
check-line-alignment: addpreserveMainDescriptionPostDelimiteroption to preserve left-hand side spacings in the main description when using thealwaysoption. (54dac34)v34.0.2Compare Source
Bug Fixes
no-bad-blocks: avoid allowing 3+ asterisks with tag content (as with only 1 asterisk) (28397c7)v34.0.1Compare Source
Bug Fixes
v34.0.0Compare Source
chore
BREAKING CHANGES
flatAPIv33.3.0Compare Source
Features
check-line-alignment: allowtagsoption to apply with "always"; #703 (4421e4e)v33.2.0Compare Source
Features
v33.1.1Compare Source
Bug Fixes
v33.1.0Compare Source
Features
v33.0.0Compare Source
chore
@es-joy/jsdoccommentforgetJSDocCommentfunctionality (aa77e3b)BREAKING CHANGES
getJSDocCommentfile.Also updates Babel devDeps.
v32.3.4Compare Source
Bug Fixes
v32.3.3Compare Source
Bug Fixes
require-param,check-param-names: do not fail with destructured array pattern containing empty slots; fixes #716 (f19e706)v32.3.2Compare Source
Bug Fixes
check-line-alignment: prevent false never reporting where a space is present (post tag) followed by missing space (from a wholly missing type) and then a space (but a space first preceded by content (a name); fixes #714 (2c31db1)v32.3.1Compare Source
Bug Fixes
check-examples: disable chai-friendly/no-unused-expressions for default expression rules (06f0112)v32.3.0Compare Source
Features
check-tag-names: jsxTags an opt-in option for jsx annotations (8afb9fc)v32.2.0Compare Source
Features
check-types: checksettings.jsdoc.structuredTagsfor an array of permissible types, reporting if not present; fixes #695 (9dad3e0)no-undefined-types: allowstructuredTagstypes to be auto-defined (b7198e4)v32.1.1Compare Source
Bug Fixes
check-param-names,require-jsdoc,require-param: avoid erring uponMemberExpressionor other constructions within dynamic properties; fixes #699 (1cfdeb4)v32.1.0Compare Source
Features
require-jsdoc: allow checking for getter or setter only; fixes #515 (937d65e)v32.0.3Compare Source
Bug Fixes
require-jsdoc: more accurate and optimized decorator detection; fixes #697 (88655b3)v32.0.2Compare Source
Bug Fixes
match-description: while preserving internal newlines, ensure trailing whitespace is stripped for comparisons; for #692 (27b95b3)v32.0.1Compare Source
Bug Fixes
uflag forcheckTypesPatternoption forrequire-param,check-param-names; forcheck-values, default touflag and allow slashed regexes with own flags; formatch-description, allow slashed regexs with own flags; for all of the previous (andcheck-examples) allows newlines (4f0dc8e)v32.0.0Compare Source
Bug Fixes
[@example](https://togithub.com/example)frommdtomd/*.js. Only applies whenmatchingFileNameis not used. (2cc1227)BREAKING CHANGES
eslint-plugin-markdownv2 and its support of ESLint 7's new processor API, fenced blocks can (and must) be targeted separately from the Markdown parent file as a whole, so in order to allow the sameoverridesconfig to be reusable between Markdown fenced blocks and@exampletags (since one often wishes to disable the same kind of rules for each, being as that each may deliberately lack full context, e.g., undefined or unused variables), we update the default simulated extension set for@exampletags bycheck-examplesto simulate an expression which will now be a suitable choice foroverridesin targeting Markdown fenced blocks using the new parser API, as with eslint-plugin-markdown@2 (i.e., "md/*.js" instead of "md").If you need to use ESLint 6 (or eslint-plugin-markdown < 2, for example) with
check-examples, you should be able to manually supply thematchingFileNameoption targeting "md", e.g., set to'dummy.md.This commit also simplifies a testing example to avoid it throwing with changed config not having proper babel support (not meaningful to test anyways)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.