-
**Error 1:**
```
Error: "Cannot read property '1' of null" while processing jsdoc comments started at line 35
-----------------------------------------------------------------------------------------…
blond updated
7 years ago
-
The issue here is the interplay of using `eslint-plugin-tsdoc` together with `prettier-plugin-jsdoc`.
Example:
```ts
/**
* @returns True if a >= b.
*/
```
Here, tsdoc will complain that
> …
beark updated
2 years ago
-
It would be nice to be able to configure an expected escaped substitution of the character sequence `*/` when used in JSDoc descriptions, types, and examples.
Example:
```json
{
"settings": …
-
## Expected behavior
Block comments that refer to org-scoped npm packages at the start of a line shouldn't be treated as JSDoc tags:
```js
/**
* @ember/debug etc. etc.
*/
```
...or at l…
-
## Expected behavior
The `jsdoc/require-param` should add exactly one new `@param` tag - one for each missing parameter.
## Actual behavior
For each missing parameter, it adds all missing param…
-
# Suggestion
## 🔍 Search Terms
`@implements` `jsdoc` `import` `export`
## ✅ Viability Checklist
My suggestion meets these guidelines:
* [x] This wouldn't be a breaking change in existin…
-
I want to:
- [x] add a new rule
- [ ] edit an existing rule
### Explanation or benefit
A minimal set of JSdoc code documentation would be nice to be enforced, as this might provide useful inform…
-
[End-of-Life for Built-in JSDoc Support in ESLint](https://eslint.org/blog/2018/11/jsdoc-end-of-life/)
> The require-jsdoc and valid-jsdoc rules will be [deprecated](https://eslint.org/docs/user-gu…
-
I'm using the lit-plugin in VSCode. I'm NOT using typescript, but instead, javascript with jsdoc type annotations.
It seems like when setting properties via the template binding, lit-plugin isn't …
-
I am trying to generate several jsdoc comments in a custom plugin.
This generation has to be triggered when a specific syntax is detected, hence I choosed the [astNodeVisitor](http://usejsdoc.org/a…