Skip to content
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

Update dependency eslint-plugin-jsdoc to v34 - autoclosed #148

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 15, 2021

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-plugin-jsdoc ^23.0.0 -> ^34.0.0 age adoption passing confidence

Release Notes

gajus/eslint-plugin-jsdoc

v34.6.0

Compare Source

Features
  • no-multi-asterisks rule to prevent multiple asterisks with middle delimiters or at end of blocks (8848246)

v34.5.0

Compare Source

Features
  • multiline-blocks: allow control of how and whether jsdoc blocks can be expressed as single or multiple line blocks (06bbf37)

v34.4.0

Compare Source

Features

v34.3.0

Compare Source

Features
  • check-values: ensure [@variation](https://togithub.com/variation) is a positive integer (56577ce)

v34.2.2

Compare Source

Bug Fixes
  • check-param-names: adjusts line numbers to be nearer problematic item (e6c9ab2)
  • no-missing-syntax: pass in missing comment (a977896)

v34.2.1

Compare Source

Bug Fixes
  • require-description, require-example: for missing description, use tag line number (310ea75)

v34.2.0

Compare Source

Features
  • no-bad-blocks: add preventAllMultiasteriskBlocks boolean option to allow reporting of any multi-asterisked multiline comments (9669fc3)

v34.1.0

Compare Source

Features
  • check-line-alignment: add preserveMainDescriptionPostDelimiter option to preserve left-hand side spacings in the main description when using the always option. (54dac34)

v34.0.2

Compare Source

Bug Fixes
  • no-bad-blocks: avoid allowing 3+ asterisks with tag content (as with only 1 asterisk) (28397c7)

v34.0.1

Compare Source

Bug Fixes
  • multiline tag fixers omitting subsequent tag lines with new command-parser API (8fa7f9b)

v34.0.0

Compare Source

chore
BREAKING CHANGES
  • Also:

  • Build: Switch to Node 12 target

  • Linting: Use flat API

  • Travis: Add Node 16, remove Node 10

  • npm: Update devDep.

v33.3.0

Compare Source

Features
  • check-line-alignment: allow tags option to apply with "always"; #​703 (4421e4e)

v33.2.0

Compare Source

Features

v33.1.1

Compare Source

Bug Fixes
  • update jsdoccomment to surface fixes (7de397b)

v33.1.0

Compare Source

Features
  • support comment-selector-based contexts (f73c72c)
  • support comment-selector-based contexts (6e835fd)

v33.0.0

Compare Source

chore
  • use external @es-joy/jsdoccomment for getJSDocComment functionality (aa77e3b)
BREAKING CHANGES
  • Should only be breaking for anyone requiring the getJSDocComment file.

Also updates Babel devDeps.

v32.3.4

Compare Source

Bug Fixes
  • preserve newlines in tag description comparisons; fixes #​692 (7edaed3)

v32.3.3

Compare Source

Bug Fixes
  • require-param, check-param-names: do not fail with destructured array pattern containing empty slots; fixes #​716 (f19e706)

v32.3.2

Compare 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.1

Compare Source

Bug Fixes
  • check-examples: disable chai-friendly/no-unused-expressions for default expression rules (06f0112)

v32.3.0

Compare Source

Features
  • check-tag-names: jsxTags an opt-in option for jsx annotations (8afb9fc)

v32.2.0

Compare Source

Features
  • check-types: check settings.jsdoc.structuredTags for an array of permissible types, reporting if not present; fixes #​695 (9dad3e0)
  • no-undefined-types: allow structuredTags types to be auto-defined (b7198e4)

v32.1.1

Compare Source

Bug Fixes
  • check-param-names, require-jsdoc, require-param: avoid erring upon MemberExpression or other constructions within dynamic properties; fixes #​699 (1cfdeb4)

v32.1.0

Compare Source

Features
  • require-jsdoc: allow checking for getter or setter only; fixes #​515 (937d65e)

v32.0.3

Compare Source

Bug Fixes
  • require-jsdoc: more accurate and optimized decorator detection; fixes #​697 (88655b3)

v32.0.2

Compare Source

Bug Fixes
  • match-description: while preserving internal newlines, ensure trailing whitespace is stripped for comparisons; for #​692 (27b95b3)

v32.0.1

Compare Source

Bug Fixes
  • default to u flag for checkTypesPattern option for require-param, check-param-names; for check-values, default to u flag and allow slashed regexes with own flags; for match-description, allow slashed regexs with own flags; for all of the previous (and check-examples) allows newlines (4f0dc8e)

v32.0.0

Compare Source

Bug Fixes
  • check-examples: change default extension for simulated file name of [@example](https://togithub.com/example) from md to md/*.js. Only applies when matchingFileName is not used. (2cc1227)
BREAKING CHANGES
  • check-examples: Per update to eslint-plugin-markdown v2 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 same overrides config to be reusable between Markdown fenced blocks and @example tags (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 @example tags by check-examples to simulate an expression which will now be a suitable choice for overrides in 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 the matchingFileName option 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)

v31.6.1

Compare Source

Bug Fixes

v31.6.0

Compare Source

Bug Fixes
  • require-returns, require-yields: support more AST checking (6fd8a07)
  • require-yields: avoid checking nested generators (as with functions) (b9058e4)
  • return-yields, return-yields-check: allow generator detection on exported; handle more AST types; fixes #​682 (4e768aa)
Features
  • require-returns-check: add exemptAsync option (0ed24c0)

v31.5.0

Compare Source

Bug Fixes
  • require-returns: check labeled statements (51f37f1)
  • require-throws: check labeled statements (ceadcfe)
  • require-yields: check test part of if expression and check conditionals (db001be)
  • require-yields: check labeled statements (aceb7a0)
Features
  • require-returns: if function returns a Promise whose executor resolves with undefined, avoid need to document unless forceReturnsWithAsync is set; fixes #​550 (565fdbd)

v31.4.0

Compare Source

Bug Fixes
  • check-line-alignment: escape user tag name in regex (c0ae4cb)
Features
  • check-line-alignment: allow tags option to configure which tags should be aligned. (780b8b5)

v31.3.3

Compare Source

Bug Fixes
  • check-line-alignment: apply alignment to return tags and avoid possibility for "never" option to insert extra space with returns/return as well as handle missing type (cb39556)

v31.3.2

Compare Source

Bug Fixes
  • while a fix provided for decorator detection and useful for inserting empty jsdoc blocks when fixers are enabled, it appears to have a 25% or so degradation in performance when tested with a large repository, so reverting. (e08d889)
Reverts
  • Revert "optimize: ensure with new fix that we avoid checking back too far" (0fc4663)

v31.3.1

Compare Source

Bug Fixes
  • bug with false positive decorator detection (evident sans semi-colons); e.g., require-jsdoc fixer (6bda6b4)

v31.3.0

Compare Source

Features
  • check-param-names: add options disableExtraPropertyReporting to allow extra properties to be documented without error (as long as there are no siblings destructured as for such cases, they will still be expected since the function is not using them) (8b2d143)

v31.2.3

Compare Source

Bug Fixes
  • require-param, check-param-names: add option useDefaultObjectProperties for expecting documentation or avoiding reporting of documented; addresses part of #​676 (a36faf2)

v31.2.2

Compare Source

Bug Fixes
  • check-tag-names: should have previously auto-allowed settings.jsdoc.structuredTags tags (5f586fd)

v31.2.1

Compare Source

Bug Fixes
  • caps issue with require-yields-check rule (6b8d0d8)

v31.2.0

Compare Source

Features
  • require-yields-check: add rule to check that yield (of proper form) is present in the function body; fixes #​354 (acf9529)

v31.1.0

Compare Source

Features
  • require-yields: add new rule to check that yield has documentation; for #​354 (e06fddd)
  • require-yields: add options to check that next has documentation (15daa12)

v31.0.8

Compare Source

Bug Fixes
  • no-undefined-types: support true and false literals (b8cb394)

v31.0.7

Compare Source

Bug Fixes
  • ensure accurate parsing of names after multi-line types; fixes #​669 (7b9c1bd)

v31.0.6

Compare Source

Bug Fixes
  • update comment-parser to surface restoration of support for equal signs in defaults and multi-line types; fixes #​669; fixes #​673 (081d7eb)

v31.0.5

Compare Source

Bug Fixes
  • require-description-complete-sentence: regression re: not trimming of description for check as relevant to tag description checking; fixes #​672 (d81caa2)

v31.0.4

Compare Source

Bug Fixes
  • restore trim as relevant to tag description checking; fixes #​670 (9f69c36)

v31.0.3

Compare Source

Bug Fixes
  • newline-after-description: handle description on same line as opening asterisks; fixes #​668 (040d177)

v31.0.2

Compare Source

Bug Fixes
  • check-line-alignment: implement default never options; fixes #​483 (b2db226)

v31.0.1

Compare Source

Bug Fixes

v31.0.0

Compare Source

chore
  • update comment-parser; should now cause fixers to preserve original whitespace unless the rule is meant to fix it (095ff36)
BREAKING CHANGES
  • Tests are not breaking, but as changing the fundamental parser, forcing major bump to be safe.

Also updates:

  1. require-description-complete-sentence - test to fix output
  2. require-hyphen-before-param-description - test to preserve whitespace in fixed output (though still minus hyphen)
  3. require-param - test preserving whitespace
    4 require-jsdoc - test with no indent

v30.7.13

Compare Source

Bug Fixes
  • require-hyphen-before-param-description: regression failing to only check for hyphen at beginning; fixes #​665 (acc3fc1)

v30.7.12

Compare Source

Bug Fixes
  • require-jsdoc: skip past type annotations when seeking backward through decorators; fixes #​659 (62abd11)

v30.7.11

Compare Source

Bug Fixes
  • no-bad-blocks: avoid erring with /* */ comment (4e6c73d)

v30.7.10

Compare Source

Bug Fixes
  • check-examples: disable no-new for check-examples and default param checking (590d54e)
  • require-hyphen-before-param-description: allow whitespace before hyphen when checking for hyphens; fixes #​664 (fb906de)

v30.7.9

Compare Source

Bug Fixes

v30.7.8

Compare Source

Bug Fixes

v30.7.7

Compare Source

Bug Fixes
  • require-jsdoc: regression causing uncommented nested syntax to be reported with publicOnly even when export was commented; fixes #​654 (bcd465f)

v30.7.6

Compare Source

Bug Fixes
  • check-examples: disable strict for expressions (245e4a7)

v30.7.5

Compare Source

Bug Fixes
  • ensure all rules marked with recommended status; add table property for recommended status; fixes #​652 (4e699c4)

v30.7.4

Compare Source

Bug Fixes
  • match-description, no-undefined-types, require-description-complete-sentence, require-hyphen-before-param-description, valid-types: parse template properly; fixes #​653 (122a9b5)

v30.7.3

Compare Source

Bug Fixes
  • check-examples: Check defaults, params, properties as expressions (6163f3c)

v30.7.2

Compare Source

Bug Fixes
  • check-examples: use jsdoc-defaults, jsdoc-params, and jsdoc-properties as default extensions to allow these to have their own overrides (39fb1cb)

v30.7.1

Compare Source

Bug Fixes
  • check-examples: Set checkDefaults, checkParams, checkProperties defaults to false (2de1011)

v30.7.0

Compare Source

Features
  • check-examples: add options checkDefaults, checkParams, checkProperties; fixes #​473 (262a474)

v30.6.5

Compare Source

Bug Fixes
  • valid-types: Ensure module tag operates as though module: prefix is present (so as to create valid namepath when valid); fixes #​649 (2e0f2a6)

v30.6.4

Compare Source

Bug Fixes
  • require-jsdoc: for publicOnly ESM, adds direct ancestor check, allowing, e.g., TSPropertySignature and TSMethodSignature; fixes #​647 (2b55275)

v30.6.3

Compare Source

Bug Fixes
  • require-jsdoc: Avoid error when comment block above export of TSDeclareFunction; fixes #​645 (0b95ba5)

v30.6.2

Compare Source

Bug Fixes
  • require-jsdoc: support TSTypeAliasDeclaration with publicOnly (42a9b35)

v30.6.1

Compare Source

Bug Fixes
  • require-jsdoc: support TSInterfaceDeclaration with publicOnly (3ae8e61)

v30.6.0

Compare Source

Features
  • add ignoreInternal setting to ignore blocks with [@internal](https://togithub.com/internal) tags; fixes #​639 (80e16d0)

v30.5.3

Compare Source

Bug Fixes
  • no-bad-blocks: ensure reports bad blocks with descriptions (9a56863)

v30.5.2

Compare Source

Bug Fixes
  • require-jsdoc: allow contexts to be usable in place of require items (a1d95e6)
  • require-jsdoc: support TSEnumDeclaration with publicOnly; fixes #​640 (63ef3bc)

v30.5.1

Compare Source

Bug Fixes
  • rename rule as intended to check-line-alignment (ec71632)

v30.5.0

Compare Source

Features
  • check-line-alignment: add rule for line alignment (#​636) (6e2b99d)

v30.4.2

Compare Source

Bug Fixes
  • check-param-names, require-param: support nested array destructuring (4f73e9c)

v30.4.1

Compare Source

Bug Fixes
  • check-param-names, require-param: properly check object parameters with default values; fixes #​635 (7fc84e9)

v30.4.0

Compare Source

Features

v30.3.3

Compare Source

Bug Fixes
  • require-param, check-param-names: check deeply destructured parameters (fixes #​569) (#​630) (428174d)

v30.3.2

Compare Source

Bug Fixes
  • check-examples: disable jsdoc/require-file-overview by default; fixes #​633 (dd4a985)

v30.3.1

Compare Source

Bug Fixes
  • no-undefined-types: avoid checking private member of scopeManager; fixes #​629 (d900a70)

v30.3.0

Compare Source

Bug Fixes
  • no-bad-blocks: allow TypeScript directive comments (41dcc19)
Features
  • no-bad-blocks: make ignored tags customizable (a1e0c13)

v30.2.4

Compare Source

Bug Fixes
  • check-param-names: avoid erring upon TSCallSignatureDeclaration; fixes #​624 (8341f97)

v30.2.3

Compare Source

Bug Fixes
  • no-defaults: adjust fixed AST to fully unset default as new comment-parser adjustment would otherwise not wholly remove the default; also updates devDeps and tests use of opening jsdoc; fixes #​568 (5cbc823)

v30.2.2

Compare Source

Bug Fixes
  • valid-types: Parse multiple names in template tags for non-jsdoc modes; fixes #​622 (7818dde)

v30.2.1

Compare Source

Bug Fixes
  • check-examples: disable jsdoc/require-jsdoc (88c93bb)

v30.2.0

Compare Source

Features
  • require-param: add checkDestructuredRoots option; fixes #​616 (3c06f09)

v30.1.0

Compare Source

Features
  • check-param-names: add checkDestructured option to allow disabling of destructured checking; fixes part of #​616 (c4d1b80)

v30.0.3

Compare Source

Bug Fixes
  • require-jsdoc: handle MethodDefinition context without erring when using exemptEmptyFunctions and exemptEmptyConstructors; fixes #​613 (08b5820)

v30.0.2

Compare Source

Bug Fixes
  • require-jsdoc: ensure conditionally checking Property/ObjectProperty/ClassProperty as parents for arrow function expressions; fixes #​612 (eac8357)

v30.0.1

Compare Source

Bug Fixes
  • require-jsdoc: avoid error with checkConstructors: false when attempting to check tags; fixes #​611 (854fb24)

v30.0.0

Compare Source

Features
  • check-types, no-undefined-types, valid-types: Add structuredTags setting to control whether the type and namepath portions should be checked for validity and whether such portions are required, and to let user-defined "namepath-defining" tags be added to defined types. Closes #​481 (89f2ad0)
  • valid-types: change allowEmptyNamepaths default to false, ensuring tags which expect names per docs will be reported (842381a)
BREAKING CHANGES
  • check-types, no-undefined-types, valid-types: Drops checkSeesForNamepaths setting. Use {settings: {jsdoc: {structuredTags: {name: 'namepath', type: false, required: ['name'],}}}} instead.

Also:
1. Clarifies in more cases where a problem is specific to the mode or not
2. Reports simultaneous invalid name and type errors
3. typdef now requires allowEmptyNamepaths: false, to report empty names (as with other tags)
4. Requires a name for event and external (and extends in jsdoc mode); some tweaking of other tags per docs

v29.2.0

Compare Source

Features
  • require-description: report more precisely the action to take when "body" descriptionStyle is set and where user has a desc/description tag; fixes #​608 (#​609) (69fd79d)

v29.1.4

Compare Source

Bug Fixes
  • check-types, no-undefined-types, valid-types: In jsdoc mode, ensure this only checked for namepath; in TypeScript or Closure, ensure this checked only for type (ef7b294)
  • check-types, no-undefined-types, valid-types: In TypeScript or Closure, add template for checking of optional type and namepath (e305cce)

v29.1.3

Compare Source

Bug Fixes
  • with fixers, create proper inner indent (of an additional space) when a tab is in use; fixes #​607 (4dfbc8d)

v29.1.2

Compare Source

Bug Fixes
  • check-param-names: ensure mismatching quoted vs. non-quoted tag name is not treated as an extra property (0c1c763)
  • require-param: Object destructuring in function parameters if key is string | number (quoted or otherwise) (1842fd2)

v29.1.1

Compare Source

Bug Fixes
  • Object destructuring in function parameters if key is string (#​599) (64e1b64)

v29.1.0

Compare Source

Features
  • check-types: allow two types (set one to the other in preferredTypes); make this the default for typescript with "object"/"Object" (82ca868)

v29.0.0

Compare Source

chore
BREAKING CHANGES
    1. Adds spaces between union items per jsdoctypeparser update.
  1. Removes JSDuck support (unions with "/" instead of "|")

Also adds support in typescript mode for readonly and intersections (X & Y)

v28.7.0

Compare Source

Features
  • require-jsdoc: add exemptEmptyConstructors and set true as default; fixes #​600 (5409f25)

v28.6.1

Compare Source

Bug Fixes
  • require-throws: arrow function expressions should check body only; fixes #​597 (e5387f1)

v28.6.0

Compare Source

Features
  • require-jsdoc: add enableFixer option; if set to false, will avoid fixer; fixes #​372 (c39fd75)

v28.5.1

Compare Source

Bug Fixes
  • valid-types: ensure checking property tags for valid namepath (0f5996b)

v28.5.0

Compare Source

Bug Fixes
  • valid-types, no-undefined-types, check-types: have mode default to typescript when typescript-eslint/parser is on; fixes #​593 (8e9195a)
Features
  • valid-types: for extends, package and access tags (e.g., private), report bracketed type in non-Closure mode; fixes #​356 (c134928)

v28.4.0

Compare Source

Features
  • valid-types, no-undefined-types: check module for namepath in non-"typescript" mode; fixes part of #​356 (947836a)

v28.3.0

Compare Source

Features
  • check-syntax: only check against Closure syntax in "jsdoc" and "typescript" mode; fixes part of #​356 (8dfdd0b)

v28.2.0

Compare Source

Features
  • check-tag-names: for "closure" mode, prefer "return" over "returns"; fixes part of #​356 (fceb74c)

v28.1.0

Compare Source

Features
  • valid-types: disallow namepath on interface tag for Closure mode; continue checking on jsdoc; fixes part of #​356 (#​587) (794aea8)

v28.0.0

Compare Source

Features
  • check-types, no-undefined-types, valid-types: use mode-aware type parsing; fixes part of #​356; fixes #​495 (6341e27)
  • check-types, no-undefined-types, valid-types: use mode-aware type parsing; fixes part of #​356; fixes #​495 (#​586) (f98a8e4)
BREAKING CHANGES
  • check-types, no-undefined-types, valid-types: Requires Node 10+

Also:
1. Adds "permissive" mode
2. Checks "param" for valid namepaths

  • check-types, no-undefined-types, valid-types: Requires Node 10+

Also:
1. Adds "permissive" mode
2. Checks "param" for valid namepaths
3. Refactors to use updated/better Node 10+ syntax/packages

v27.1.2

Compare Source

Bug Fixes
  • require-jsdoc: place comment block above any decorators; fixes #​571 (d5f8159)

v27.1.1

Compare Source

Bug Fixes
  • no-undefined-types: if no scope found, resume checking current node for template tags; fixes #​578, fixes #​579 (fed7586)

v27.1.0

Compare Source

Features

v27.0.7

Compare Source

Bug Fixes
  • check-param-names, require-param: handle ts constructor as arg; fixes [#​576](https://togithub.com

Configuration

📅 Schedule: 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.


  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot changed the title Update dependency eslint-plugin-jsdoc to v34 Update dependency eslint-plugin-jsdoc to v34 - autoclosed Jun 6, 2021
@renovate renovate bot closed this Jun 6, 2021
@renovate renovate bot deleted the renovate/eslint-plugin-jsdoc-34.x branch June 6, 2021 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant