Motivation
Current behavior
Should take a look at https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/eslint-plugin to see if its rules can be adapted for use with JSDoc, and if not, consider a multiple processors approach.
Desired behavior
Be able to lint TypeScript types within TypeScript-style JSDoc, e.g., to use consistent styling of semicolons or commas as separators, etc.
Rules ripe for adaption:
Also:
Less likely but possible:
Alternatives considered
Using typescript-eslint plugin if supported.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Motivation
Current behavior
Should take a look at https://github.com/typescript-eslint/typescript-eslint/tree/main/packages/eslint-plugin to see if its rules can be adapted for use with JSDoc, and if not, consider a multiple processors approach.
Desired behavior
Be able to lint TypeScript types within TypeScript-style JSDoc, e.g., to use consistent styling of semicolons or commas as separators, etc.
Rules ripe for adaption:
function()@typeannotation precedes the structure)Also:
no-incompatible-jsdocto forbid the likes ofmodule:andexternal:namepaths which are not understood by TS even if not rejected by it.Less likely but possible:
anyanywhere)Alternatives considered
Using typescript-eslint plugin if supported.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.