chore(deps): bump eslint-plugin-jsdoc from 31.6.1 to 32.0.0

[dependabot]

Bumps eslint-plugin-jsdoc from 31.6.1 to 32.0.0.

Release notes

Sourced from eslint-plugin-jsdoc's releases.

v32.0.0

32.0.0 (2021-02-15)

Bug Fixes

• check-examples: change default extension for simulated file name of [@example](https://github.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)

Commits

• 2cc1227 fix(check-examples): change default extension for simulated file name of `@ex...
• bc391f3 chore: update devDep. (gitdown)
• aefc1c1 chore: update eslint devDep and semantic-release; resume using :has() selec...
• 547a1c9 docs: clarify comment on options structure
• 08e76b1 chore: update devDeps (besides husky which is temporarily changing its licens...
• b42bf79 docs: create separate template for documentation bugs
• ae0112c docs: clarify that not all rules expect a single object option; fix a few rul...
• 9f757aa refactor(check-line-alignment): drop redundant replacements per `comment-pa...
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)