Skip to content

Testing: Transition away from ESLint valid-jsdoc rule #13741

@aduth

Description

@aduth

Related: eslint/eslint#11145
Related: https://eslint.org/blog/2018/11/jsdoc-end-of-life

Per the above links, ESLint is undergoing a deprecation of built-in support for JSDoc. As such, we should consider preemptively switching to another plugin, such as eslint-plugin-jsdoc. As a side-effect, this could greatly expand the specific enforcement we'd like to see, in order to more closely align with JavaScript Documentation Standards.

I came across the discovery of the deprecation as a result of its buggy behavior (example), which can be further motivation for expediting a transition.

Metadata

Metadata

Assignees

Labels

Good First IssueAn issue that's suitable for someone looking to contribute for the first timeNeeds DevReady for, and needs developer efforts[Status] In ProgressTracking issues with work in progress[Tool] ESLint plugin/packages/eslint-plugin[Type] Automated TestingTesting infrastructure changes impacting the execution of end-to-end (E2E) and/or unit tests.[Type] Build ToolingIssues or PRs related to build tooling[Type] TaskIssues or PRs that have been broken down into an individual action to take

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions